On 10 September 2014 16:15, Anton Tanasenko <[email protected]> wrote:
> Hi, > As I understand, it is PDE that manages Plug-in dependencies and resolves > workspace plugins, m2e basically only provides ways for tycho to configure > the project correctly. > You should expect the following nature in .project (in addition to java > and m2e ones): <nature>org.eclipse.pde.PluginNature</nature> > And following .classpath entry: <classpathentry kind="con" > path="org.eclipse.pde.core.requiredPlugins"/> > > I haven't used felix bundle plugin, so it might be different from pure > tycho based approach. > Thanks! Your information was enough for me to find what I want via google "maven-bundle-plugin m2e export bundle" http://www.subshell.com/en/subshell/blog/Referencing-Maven-projects-from-Eclipse-plugins100.html says to add this for m2e. After adding this to the three bundle projects, and running Maven > Update Project... on all of them and the RCP plugin, it works as expected. <pluginManagement> <plugins> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself. --> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId>org.apache.felix</groupId> <artifactId>maven-bundle-plugin</artifactId> <versionRange>[1.0.0,)</versionRange> <goals> <goal>manifest</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement>
_______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
