I use pde + maven-bundle-plugin + osgi framework launcher but i don't use mvn-eclipse-plugin. You should be using m2e, which works completely different than m-eclipse-p. Just do a final eclipse:clean and forget about that plugin.
Then make sure that your eclipse has m2e (comes by default with any recent eclipse) and do a File > import > maven > Existing Maven project if your project is already in the filesystem. If not choose "checkout maven project from SCM" instead good luck Alejandro Endo | Software Designer/Concepteur de logiciels From: Jennifer Vendetti <vende...@stanford.edu> To: users@maven.apache.org, Date: 2013-10-23 03:49 PM Subject: mvn-eclipse-plugin problem with pde projects and linked resources Hello, I just took over the maintenance of several OSGi bundles. I added the mvn-eclipse-plugin to the POM files for each of the bundles because I'd like to generate the necessary Eclipse project files to work with the source code and use the OSGi Framework launcher in the Eclipse IDE: <plugin> <artifactId>maven-eclipse-plugin</artifactId> <version>2.9</version> <configuration> <pde>true</pde> </configuration> </plugin> For reasons I don't understand, running "mvn eclipse:eclipse" generates a .project file with an incomplete set of linked resources. For example, I have a POM file for one of the bundles that has the following 3 dependencies: <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.17</version> </dependency> <dependency> <groupId>org.apache.felix</groupId> <artifactId>org.apache.felix.main</artifactId> <version>4.2.1</version> </dependency> <dependency> <groupId>com.jgoodies</groupId> <artifactId>looks</artifactId> <version>2.2.2</version> </dependency> The generated .project file for this bundle only has one linked resource to one of the artifacts: <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>org.protege.common</name> <comment>Core Protege Libraries. NO_M2ECLIPSE_SUPPORT: Project files created with the maven-eclipse-plugin are not supported in M2Eclipse.</comment> <projects/> <buildSpec> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> </buildCommand> <buildCommand> <name>org.eclipse.pde.ManifestBuilder</name> </buildCommand> <buildCommand> <name>org.eclipse.pde.SchemaBuilder</name> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.jdt.core.javanature</nature> <nature>org.eclipse.pde.PluginNature</nature> </natures> <linkedResources> <link> <name>looks-2.2.2.jar</name> <type>1</type> <location>C:/Users/vendetti/.m2/repository/com/jgoodies/looks/2.2.2/looks-2.2.2.jar</location> </link> </linkedResources> </projectDescription> When I try to import the existing PDE project into Eclipse, I get compiler errors since the other two artifacts aren't listed as linked resources. Is there something I'm missing about how to properly use this plug-in? I'm using Maven version 3.1.0. Any help and/or advice would be very much appreciated. Jennifer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org DISCLAIMER: Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.