After much grepping I figured out that the maven-bundle-plugin will not force things to fail if I set:
-failok: true in the osgi.bnd file for the wrapped jar. This works, although all of the 1.0 packages appear to get exported along with everything else. Probably not the best solution, but it works for now. thanks, Mike On Tue, May 20, 2008 at 1:37 PM, Niclas Hedhman <[EMAIL PROTECTED]> wrote: > On Wed, May 21, 2008 at 2:27 AM, Mike Smoot <[EMAIL PROTECTED]> wrote: > > > pax-wrap-jar -g com.sun.xml.bind -a jaxb-xjc -v 2.0 > > > Any thoughts on what might be going on here and how I can work around it? > > My guess is that the jaxb-xjc packager thought that it would be a good > idea to ship ver1.0 code as part of the ver2.0 jar, maybe for > compatibility reasons. If you check inside, you will probably see > differences between the com/* and 1.0/com/*. > > I don't know Pax Construct well enough to know what options one have. > An "Ignore=" would of course be really good. Otherwise, perhaps > hooking into the Maven build cycle and remove the 1.0/ directories ?? > > > Cheers > Niclas > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- ____________________________________________________________ Michael Smoot, Ph.D. Bioengineering Department tel: 858-822-4756 University of California San Diego
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
