Release bundle jars using incorrect version number within filename

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.3.0 CE GA1, Master
• Fix Version/s: 7.0.10.13 DXP SP13, 7.0.X, 7.1.X, 7.2.X, 7.3.1 CE GA2, 7.3.2 CE GA3, 7.3.10 DXP GA1, Master
• Component/s: Dev Tools > Portal Build Env
• Labels:
  • 7.3-known-issues
  • liferay-dxp-70-sp13
  • liferay-fixpack-de-90-7010
  • liferay-fixpack-dxp-17-7110
  • liferay-fixpack-dxp-5-7210
  • liferay-ga1-ce-730
• Branch Version/s:
  7.3.x, 7.2.x, 7.1.x, 7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/shuyangzhou/liferay-portal/pull/8926

For example, the jar within Liferay CE Collaboration - Liferay CE Wiki - API.lpkg is named com.liferay.wiki.api-5.0.3.jar when it should be named com.liferay.wiki.api-5.0.2.jar as that includes its actual version number (the version that is actually published on Nexus). charles.austin confirmed the jars in the bundle are the same as the ones that are published on Nexus despite the name difference.

The logic in build-app-module.xml is incorrectly renaming jars because it uses the version within the module's bnd.bnd which doesn't include the published version.