Hi Stuart, On 21 November 2011 15:38, Stuart McCulloch <[email protected]> wrote: > On 21 Nov 2011, at 15:11, David Bosschaert wrote: >> >> What happens at the moment with the Maven Bundle Plugin 2.3.4 (we >> can't use 2.3.5 as it has a different bug > > ^ have you reported that bug on JIRA? If not then please do it soon > otherwise it won't make it into the 2.3.6 release
Yes, it's: https://issues.apache.org/jira/browse/FELIX-3058 >> ) is that all the classes >> from org.acme.foo that exist in bundle B are copied into the resulting >> bundle A. >> >> This should not happen. I tried a number of things to exclude the >> classes from bundle B appearing in bundle A but none of them seem to >> work. Anyone an idea how to prevent this? > > Have you tried: > > Export-Package: blah;-split-package:=first > > This tells BND to use the contents of the first definition of the "blah" > package (which should be the one from the local "target/classes") instead of > merging. Adding that doesn't help. I've updated my test setup at https://github.com/bosschaert/coderthoughts (branch: split-package) with the directive but the bundle generated in ascii-pics-provider-bundle-mbp still contains org.coderthoughts.asciipics.impl.RogueClass from the ascii-pics-api-bundle-mbp bundle... Any further help much appreciated! David --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
