Open kthoms opened 5 years ago
We have several places in pom.xml files that define lifecycle mappings for m2e. These mappings are quite verbose, e.g.
<plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId> org.codehaus.mojo </groupId> <artifactId> exec-maven-plugin </artifactId> <versionRange> [1.2.1,) </versionRange> <goals> <goal>java</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin>
With m2e 1.7 this can be simplified. Usually we exclude plugins from mappings which would correspond now with the entry
<?m2e ignore?>
see also https://www.eclipse.org/lists/tycho-user/msg08357.html
move to 2.22
move to 2.24
We have several places in pom.xml files that define lifecycle mappings for m2e. These mappings are quite verbose, e.g.
With m2e 1.7 this can be simplified. Usually we exclude plugins from mappings which would correspond now with the entry