Hi Stuart Thanks, that works. However it still seems quirky to me. Maybe a warning on the documentation page, explicitly highlighting this? I've come across this too many times and I thought it was a bug. Clearly from this, and past discussions on the bnd plugin, this behaviour is too important to try and "fix", so it should be documented at least.
Thanks Chris On Mon, 2009-05-04 at 13:35 +0800, Stuart McCulloch wrote: > 2009/5/4 Christopher Armstrong <[email protected]> > ... > > > > How can cause maven-bundle-plugin to not export the org.test package? My > > understanding of the Private-Package header is that it doesn't export > > all the packages specified for it. > > > "If a package is selected by both the export and private package headers, > then the export takes precedence." > > so if you only set Private-Package then you'll still have the default export > setting which will take precedence > (you can confirm this by using "mvn -X clean install" to output the final > processed instructions sent to BND) > > because the default Private-Package now includes all the Java files under > "src/main/java" you could just use: > > <instructions> > <Export-Package/> > </instructions> > > of course this particular situation isn't so straightforward because of the > precedence between export + private :( > > [1] http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html > > > > I've attached the project I am using. My maven version is 2.09. > > > > Thanks > > Chris > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
