Hi, I would discourage using the the project version as the version for the package exports. See [1] for the full discussion of the topic.
For short: In general packages and bundles do not evolve in the same way. Particularly some exported packages of a bundle may not evolve while other (exported or not) packages evolve. This causes the bundle and its version to evolve, of course. But then the version of the unmodified exported package should not be increased, otherwise your downstream users of the bundle will be confused and in fact may fail to update the bundle due to import constraints. Regards Felix [1] http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf Am Donnerstag, den 11.11.2010, 17:32 +0100 schrieb Manuel Innerhofer: > Hi, > We have several bundle projects sharing the same parent. I'd like to > configure BND in the > parent the way that each bundle exports its local Java sources with the > version attribute set > to the pom version (of the bundle project). The default behaviour of > <Export-Package> exports > the correct packages, but without the version attribute set. Is there a way > to have the default > behaviour, but with versions? I imagine a solution would look similar to > this: > > <Export-Package>${local.java.sources};version="${pom.version}"</Export-Package> > > We are using the maven bundle plugin 2.1.0. > Thanks in advance. > > Regards, > Manuel --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
