Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
maven-bundle-plugin-1.4.3
-
None
Description
The current release of the plugin uses bndlib version 0.0.255.
In this version there is a bug converting valid OSGi Bundle-Version values to a different one.
A short summary: In my company we have a unusual versioning scheme - here is one example:
1.3.0.0-0-01-0
in development cycles extended by -SNAPSHOT: 1.3.0.0-0-01-0-SNAPSHOT. Both versions are - from the point of view of the OSGi spec - a valid Bundle-Version value (see the API here: http://www.osgi.org/javadoc/r4v41/org/osgi/framework/Version.html#Version(java.lang.String)).
In spite of this fact the maven-bundle-plugin (resp. bndlib) converts it to
1.3.0.0
or - when using -SNAPSHOT - 1.3.0.SNAPSHOT.
I already asked Peter Kriens to fix that and he quickly came up with a fix (version 0.0.293, to be downloaded from http://www.aqute.biz/repo/biz/aQute/bndlib/0.0.293/bndlib-0.0.293.jar).
I tried to replace the bndlib dependency with the new version. Unfortunately there seems to have been a significant change in the API of bndlib:
java.lang.NoClassDefFoundError: aQute/lib/reporter/Reporter
at org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:360)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:273)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:227)
at org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:218)
Since it's not acceptable that a valid Bundle-Version is modified and I cannot use the most current version of bndlib, I ask you to update the maven-bundle-plugin to use a newer version of bndlib to fix the bug I mentioned above.
Thank you!
Regards,
René