| [m2e-users] feedback M2E Ingio - m2e connector concept |
Just tried out our build environment with Indigo and m2e 1.0.0.20110607-2117. User-experience : After a full import of all maven projects, I’ve received following error in almost every pom: Plugin execution not covered by lifecycle configuration: … After clicking around for some time, I found under pom.xml / Overview the possibility to ignore those «not covered plugin-lifecycles » Unfortunately, this modified my pom and added : <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> … </configuration> </plugin> </plugins> </pluginManagement> In the import wizard, after m2e didn‘t found lifecycle connectors, there should be a combobox in the Action column displayed BEFORE the user clicks an cell. Otherwise it’s not easy to unterstand that this cell is editable. Opinion : In my view, is the attempt to store M2e settings within a platform and !IDE! independent element, such as pom.xml utterly the wrong place! I’m using maven because it is an independent build tool, which does not care what is used for developing or building maven projects! Even if maven or other IDE’s don’t care for those excludes (eventually..), I don’t wanna be forced to edit all my pom’s or at least the parents (If you got any..) for developing with Eclipse. Is there a possibility to disable this new m2e connector feature by default ? My suggestions: - Store m2e connector excludes anywhere but in the pom.xml - Disable m2e connector feature by default - Documentation for m2e connectors (what are the advantages ?) Just my two coins, Regards Christian |