I think its important to consider that Camel moving to bnd-maven-plugin
will mean most users will do the same, or inherit their projects from a
camel-parent pom or camel-bom. I suggest that end-user Camel projects be
included as a use case, along with the Camel source tree itself.
On 4/5/16 1:58 PM, Quinn Stevenson wrote:
I’ve got the basics down for doing this conversion, but there are a couple of
differences between the MANIFEST.MF files generated by the two tools when
SNAPSHOT versions are used.
Bundle-Version header:
By default, given a version in a POM like "1.2.3-SNAPSHOT”:
- the maven-bundle-plugin converts the version to “X.X.X.SNAPSHOT"
- the bnd-maven-plugin changes the version "X.X.X.<timestamp>"
There is a new instruction in the upcoming 3.2.0 release of the
bad-maven-plugin that will allow preserving the “.SNAPSHOT” in the
Bundle-Version header.
I’m assuming we want to preserve the “.SNAPSHOT” in the Bundle-Version header,
so we’ll need to wait for version 3.2.0 of the bnd-maven-plugin
+1 .SNAPSHOT should be maintained vs timestamp.
Export-Package header:
- the maven-bundle-plugin includes “.SNAPSHOT” in the version of exported packages
- i.e. org.apache.camel;version=“2.18.0-SNAPSHOT"
- the bnd-maven-plugin does not include “.SNAPSHOT” in the version of the
exported packages - i.e. org.apache.camel;version=“2.18.0”
The bad-maven-plugin can be configured to do this by adding a “packageinfo”
file for every exported package
Do we need to keep the “.SNAPSHOT” in the exported package versions?
I believe this may be OSGi runtime specific, but I know having a
.$OTHERSTUFF after the X.Y.Z is valid in Karaf+Felix.
Interesting idea using the "2.18.0" for exports on packages. I could see
that being handy.
-Matt
