[ 
https://issues.apache.org/jira/browse/KARAF-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158194#comment-13158194
 ] 

Andreas Pieber commented on KARAF-1048:
---------------------------------------


I finally had a chance to evaluate the problem on an empty eclipse 3.7.1. It's 
as simple as

a) download eclipse 3.7.1 for java developers (or any other distribution)
b) checkout karaf source
c) import as existing maven project
d) Use autoresolve to install the existing plugins

This problem can be easily resolved by adding the Andrei's "patch" to the Karaf 
root pom. It's as the plugin itself states (if you let it autogenerate the 
section in the root pom): "This plugin's configuration is used to store Eclipse 
m2e settings only. It has no influence on the Maven build itself." I don't say 
that I like that those environment specific settings are stored in the pom, 
it's just that I don't consider them harmful as long they require only a small 
section in the root pom.

This is also not really related to our plugins; we might provide own mappers 
for m2e but I not right now I think since other projects using Karaf can simply 
exclude them as we would do here for the maven-bundle-plugin.

I don't say that I'm happy with what sonatype is doing here! We would 
definitely have to be very careful here to not integrating them any further; 
but for now I consider them as "not harmful"... Therefore I'm still +1.

we might still want to bring this topic to the dev list getting a little bit 
more feedback first? I think a poll might be a little bit over-engineering of 
the problem :-)
                
> 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

        

Reply via email to