Hello,
I have a maven module with with two packages that I build as a bundle using
the maven-bundle-plugin. Depending on the contents of the <Export-Package>
tag of the plugin configuration I get more or less consistent results.
The most confusing (to me) is this one:
<Export-Package>{local-packages};version="${project.version}</Export-Package>
The project version is 3.0.0-SNAPSHOT. This yields the following
Export-Package section in the Manifest:
Export-Package: ch.vivates.ams.camel.compoment.uldap;uses:="ch.vivates.a
ms.camel.compoment.uldap.unboundid,org.apache.camel,org.apache.camel.im
pl";version="3.0.0",ch.vivates.ams.camel.compoment.uldap.unboundid;vers
ion="3.0.0.SNAPSHOT";uses:="com.unboundid.ldap.sdk"
Note that the package "ch.vivates.ams.camel.compoment.uldap" is exported as
version 3.0.0. The second package
"ch.vivates.ams.camel.compoment.uldap.unboundid" as version 3.0.0.SNAPSHOT.
Using <Export-Package>{local-packages}</Export-Package> the version for both
packages is set to 3.0.0.
Using
<Export-Package>ch.vivates.ams.camel.compoment.uldap.*;version="${project.version}</Export-Package>
the version is 3.0.0.SNAPSHOT for both packages.
Now, which is a bug and which is expected behavior?
Is it expected behavior that version 3.0.0 and not 3.0.0.SNAPSHOT is used if
the version directive is not present in <Export-Package>?
BTW: This is the module that also gives me a headache as a dependency in the
context of this question
<http://apache-felix.18485.x6.nabble.com/Import-missing-tp5010122.html> .
Maybe this helps to find my mistake?
Thanks,
Ralf
--
View this message in context:
http://apache-felix.18485.x6.nabble.com/Export-Package-with-local-packages-yields-version-mix-tp5010124.html
Sent from the Apache Felix - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
