[
https://issues.apache.org/jira/browse/KARAF-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157982#comment-13157982
]
Glen Mazza commented on KARAF-1048:
-----------------------------------
Andrei, re (2), I don't see how "mvn eclipse:eclipse" can be legacy w.r.t. m2e,
as it never needed m2e to begin with. Further, it's a plugin that creates
classpath and project files that Eclipse can use, so it's not an issue of
Eclipse supporting it but of the plugin being up-to-date and creating project
files that Eclipse can use. I don't see any indication from the Maven site
that the Maven Eclipse plugin
(http://maven.apache.org/plugins/maven-eclipse-plugin/) is going to be retired
and no longer maintained/updated.
> make pom.xml eclipse 3.7 m2e friendly
> -------------------------------------
>
> Key: KARAF-1048
> URL: https://issues.apache.org/jira/browse/KARAF-1048
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Reporter: Andrei Pozolotin
>
> currently it is impossible to import karaf projects from svn in
> eclipse 3.7 with m2e integration w/o need to manually
> provide m2e life cycle entries such as this,
> for all kinds of 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>
> [2.3.5,)
> </versionRange>
> <goals>
>
> <goal>cleanVersions</goal>
> </goals>
> </pluginExecutionFilter>
> <action>
>
> <ignore></ignore>
> </action>
> </pluginExecution>
> </pluginExecutions>
> </lifecycleMappingMetadata>
> </configuration>
> </plugin>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
