Legacy Knowledge Base
Published Jul. 2, 2025

Bundle-Version differences in fixpacks

Written By

Mariano Alvaro

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • Why do Bundle-Version differ between MANIFEST.MF in fixpack binaries and the source code?

Environment

  • Liferay DXP 7.0+

Resolution

To briefly explain the reason it must be clarified the way .jar files are released and fix pack source is packaged.

  • When releasing all the binaries are published and afterwards a .lpkg, from those published binaries, is prepared in order to perform regression testing. Meanwhile all bnd.bnd files are incremented with a "prep next" commit message to indicate that version x.y.z has been released, so everything that comes after that release is preparing for x.y.z+1 release.

  • The difference in versions gets generated from the way the tag get assigned after the increment, rather than before the increment. The reason is that the source at the tag is what gets bundled, not the source immediately before the publish, since there can be modifications needed from the publishing until the packaging if some bugs are found during the regression testing.

So the best way to know which module version is truly using a fixpack is to check the Release Notes and watch for the Module Version Changes between fixpacks.

 

Did this article resolve your issue ?

Legacy Knowledge Base