[
http://jira.magnolia-cms.com/browse/BUILD-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated BUILD-72:
--------------------------------
Description:
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 ...
{code}
<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>{code}
The bug is being discussed at
https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
was:
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 ...
{code}
<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>{code}
> Support for m2e / Eclipse Indigo ?
> ----------------------------------
>
> Key: BUILD-72
> URL: http://jira.magnolia-cms.com/browse/BUILD-72
> Project: Build
> Issue Type: Task
> Components: poms
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Fix For: POMs 23
>
>
> 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 ...
> {code}
> <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>{code}
> The bug is being discussed at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
