Nicolas,
Current ugly workaround to this problem is to import all required
springsource bundles as binary project into workspace
(File->Import...->Plug-ins and Fragments).
Also, we are working to provide first class support for OSGi development
with Maven, so stay tuned ;-)
Nicolas Jouanin wrote:
Hi,
I'm currently developing an eclipse RCP application. This application
consists of eclipse plugins also known as bundles. In this project,
maven integration means that every bundle is a maven module with its own
pom.xml.
Now it happens that some of my bundles depends on other bundles like
spring-dm or XStream. Therefore, in pom.xml I have for example:
<dependency>
<groupId>com.thoughtworks.xstream</groupId>
<artifactId>com.springsource.com.thoughtworks.xstream</artifactId>
<version>1.2.2</version>
</dependency>
This artifact exists in my local repository.
In eclipse IDE, in the package explorer,
com.springsource.com.thoughtworks.xstream appears in the maven
dependencies list and there are no compilation error. BUT, eclipse
complains because, my bundle specifies Import-Package:
com.thoughtworks.xstream in its MANIFEST.MF, but it can't find any
bundle exporting it. It seems that eclipse only looks for exported
package in the runtime environment, and not in MAVEN dependencies.
I don't know if I'm clear and if this mailing list if the good place for
asking, but may be some other people have exprience with eclipse bundle
dev. integration with maven and eclipse.
Thanks,
Nicolas.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
