I don't know if this is intended or not, but it isn't surprising to me. As an aside, I would be VERY careful about the version of packages contained in the JDK/JRE. In general, the version numbers for JRE packages isn't defined. Check the list archives for both felix-users and osgi-dev for past discussions of this.
Justin On 9/27/10 12:17 PM, [email protected] wrote: > > > Using maven-bundle-plugin version 2.1.0, in my import package I have the > following: > > > > <Import-Package> > > <!-- JDK imports --> > > javax.xml.*;version="1.6", > > <!-- JAXB imports --> > > javax.xml.bind.*;version="2.1.0", > > javax.xml.bind.annotation.*;version="2.1.0" > > </Import-Package> > > > > > > In the MANIFEST.MF file that is generated, I see the following: > > > > Import-Package: > javax.xml;version="1.6",javax.xml.bind;version="1.6",javax.xml.bind.annotation;version="1.6" > > > > > > > So, it appears if a parent package is defined first, then all child packages > are automatically given the parent's version number. However, if I change > the order in the import package area, I can get the desired effect. The > following: > > > > <Import-Package> > > <!-- JAXB imports --> > > javax.xml.bind.*;version="2.1.0", > > javax.xml.bind.annotation.*;version="2.1.0" > > <!-- JDK Imports --> > > javax.xml.*;version="1.6" > > </Import-Package> > > > > Produces: > > > Import-Package: > javax.xml;version="1.6",javax.xml.bind;version="2.1",javax.xml.bind.annotation;version="2.1" > > > > > Is this the intended behaviour? If so, why? > > > > v/r, > > > > Mike Van --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
