sysdeo plugin request a forked generate-resource phase that is not required
---------------------------------------------------------------------------
Key: MOJO-1082
URL: http://jira.codehaus.org/browse/MOJO-1082
Project: Mojo
Issue Type: Bug
Components: sysdeo-tomcat
Reporter: nicolas de loof
I use a custom profile to make projects setup easier : running "mvn -Psetup"
creates all the required configuration
<profile>
<id>setup</id>
<build>
<defaultGoal>validate</defaultGoal>
<plugins>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<executions>...</executions>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>sysdeo-tomcat-maven-plugin</artifactId>
<executions>...</executions>
</plugin>
</plugins>
</build>
</profile>
This has the unexpected side-effect that both eclipse and sysdeo plugin fork an
execution. When execution forks for the sysdeo plugin, the eclipse plugin
doesn't retrieve the executedProject instance it depends on.
>From the plugin source code, the sysdeo plugin has no requirement for the
>executedProject as it only relies ${project} and basedir.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
