Hi Stuart, > <Embed-Dependency>*;scope=compile;inline=true</Embed-Dependency> > BTW, the reason your setup worked with the old > maven-osgi-plugin was because it assembled the bundle > contents in the output folder (ie. target/classes) before > finally jar'ing everything up - and in Maven, any dependent > projects in the same reactor use the 'target/classes' > directory instead of the artifact file
I already wondered why it worked with the osgi-plugin in the first place and this explains it. > with the bundle-plugin, because the Bnd tool assembles the > bundle in memory, there's no unpacked content under > 'target/classes' to match the classpath that Maven passes to > the unit tests - however you can get this by using the maven > dependency plugin to unpack the bundle (ie. either unpack it > to 'target/classes' > in the bundle project or the unit test project) > > HTH Yes, it does :) Thanks. Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
