Aaron Siri wrote:
I'm wondering if it'll resolve classes that are in a dependency bundle.
Well, I am still not clear as to what you are saying. Best way to figure
it out is to create a simple example and see if it does what you expect.
Also, I specified my own manifest file via the <manifestFile> tag but it
seems to be ignored (at least nothing in that file has been put into the
manifest file in final .jar).
Hmm. Not sure on this issue, since I never used the manifestFile
option...I always just put everything in the pom file...and now I use
the new bundle plugin...
-> richard
-Aaron
-----Original Message-----
From: Richard S. Hall [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 3:02 PM
To: felix-dev@incubator.apache.org
Subject: Re: maven-osgi-plugin follow bundle dependencies?
Aaron Siri wrote:
I'm wondering if the maven-osgi-plugin will properly add
Bundle-Classpath entries from dependencies to the classpath when doing a
compile?
Specifically, can you specify a bundle as a maven dependency and have
the plugin do the right thing with the classpath entries in the
manifest from the dependencies when compiling.
If I understand your question correctly, yes you can have the plugin
automatically embed your dependent JAR files inside of your bundle and put
them on the bundle class path. See the "Advanced Features" section of this
document:
http://cwiki.apache.org/FELIX/osgi-plugin-for-maven-2.html
The new maven bundle plugin uses a different approach where you simply
specify which packages on the compile-time class path should be include in
your bundle. Its documentation is here:
http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html
-> richard
