2008/9/8 Sahoo <[EMAIL PROTECTED]> > I am using maven-bundle-plugin v.1.4.3. I see that even though a bundle > exports 0.3.18 of a package, the Import-Package header only contains 0.3 as > the version. I have attached a simple test case to bug #549 [1]. There is no > packageversion file, so information is encoded in manifest file only. > > The relevant portion of generated manifest for both the artifacts are given > below: > > A2/target/classes/META-INF/MANIFEST.MF > ---------------------------------------------------------- > Import-Package: p;version="0.3.18" > Export-Package: p;version="0.3.18" > > A1/target/classes/META-INF/MANIFEST.MF > ----------------------------------------------------------- > Import-Package: org.osgi.framework;version="1.3",p;version="0.3" > > bnd document suggests that micro part should be used; only qualifiers are > dropped. Is this a bug in plugin or bnd? I need a fix/work around rather > soon. >
I'll need to dig into the BND source to confirm this is a bug (unless Peter beats me to it) also note that I'm still waiting for the latest version of BND to be uploaded to the Maven central repository (http://jira.codehaus.org/browse/MAVENUPLOAD-2187) for the last few weeks, and this update also brings in several other changes - so imho a quick fix is very unlikely what with time needed for testing, etc. the simple workaround would be to manually fix the version to the micro level - but note that version="0.3" is short for version="[0.3,∞)" which does include the "0.3.18" version so you might find that the trimmed version still works for you do you see any exceptions / problems when you use the bundle with the trimmed version? Thanks, > Sahoo > > [1] https://issues.apache.org/jira/browse/FELIX-549 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
