Neutral The latest version of Eclipse (Indigo) introduces m2e 1.0, which seems to cause some problems with plugins that are not "known" by m2e.
This hits us with our setproperty plugin.
Background info:
- http://wiki.eclipse.org/M2E_plugin_execution_not_covered
- http://dev.eclipse.org/mhonarc/lists/m2e-users/thrd7.html starting at http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00448.html
It would seem that adding the following to our parent pom might "solve" the issue. It doesn't seem like the most elegant thing, though ...
<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>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>info.magnolia</groupId>
<artifactId>maven-setproperty-plugin</artifactId>
<versionRange>[1.1.1,)</versionRange>
<goals>
<goal>set-property</goal>
</goals>
</pluginExecutionFilter>
<action>
<execute></execute>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
The bug is being discussed at https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
- is related to
-
BUILD-108 Fix and update org.eclipse.m2e lifecycle-mapping
-
- Closed
-
