Mike- Please keep reply on-list and without thread trimming... I didn't actually mean to hit send because this seemed to warrant a longer response than I was prepared to give at the time.
First off, yes, I was answering your question in the context of maven-bundle-plugin. Wildcards are perfectly legal (and very useful) in the context of this plugin, but you have to understand what they mean. When you write <Import-Package> org.springframework.jndi.*;version="3.0.3.RELEASE" </Import-Package> You are telling BND (which maven-bundle-plugin wraps) to analyze your classes and for any necessary import which begins with org.springframework.jndi, specify a version of 3.0.3.RELEASE. This only works if your classes reference this package. According to your email, this isn't the case. Instead, what you want is: <Import-Package> org.springframework.jndi;version="3.0.3.RELEASE",* </Import-Package> Which tells BND to perform its analysis and ADD (if it isn't there already) org.springframework.jndi to the list of imports with that specific version. It is a subtle, but important, difference. Wildcards won't cause imports to be added which aren't referenced from your code. Note - this is a bit of a simplification in that BND will also analyze embedded JARs, but hopefully this is enough to get you started. Justin On 9/27/10 12:56 PM, [email protected] wrote: > Justin, > > > > I should have been clearer, I was speaking about the > maven-bundle-plugin, not the MANIFEST.MF file. Does your suggestion > work with the maven-bundle-plugin as well as the MANIFEST.MF file? > > > > v/r, > > > > Mike Van > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
