[
https://issues.apache.org/jira/browse/KARAF-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber updated KARAF-1048:
----------------------------------
Fix Version/s: (was: 2.2.5)
OK, I've reverted my last patch since it breaks the build; there are quite more
issues/fixes included here. Making the project easy to import in eclipse is not
done by only adding the m2e stuff but only by cleaning up the entire pom
structure. Therefore I'm sorry but I think I won't fix this on the 2.x branch
because of the real work load. In addition I'm a little bit afraid of changing
the pom structure for a micro release branch tbh. Maybe for 2.3.0. 3.0.0 should
be eclipse friendly soon though.
> 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
> Affects Versions: 2.2.4, 3.0.0
> Reporter: Andrei Pozolotin
> Assignee: Andreas Pieber
> Fix For: 3.0.0
>
>
> 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
