Henri,
m2e does not currently support workspace mojo execution during project
clean and related operations. The workaround is to install the mojo into
local repository. See http://jira.codehaus.org/browse/MNGECLIPSE-645
Henri Gomez wrote:
Henri,
Hi Eugene.
I don't see the error in your details.
0/1/08 6:18:41 PM CEST: Build errors for
mycorp-am-webapp;org.apache.maven.lifecycle.LifecycleExecutionException:
Failed to construct build plan for: mycorp-am-webapp
Id: org.mycorp.am:mycorp-am-webapp:war:1.1.0
task-segment: [process-test-resources]. Reason: Failed to resolve
plugin for mojo
binding:org.mycorp.mojo:translator-maven-plugin:1.0-SNAPSHOT:translator
Anyway, it is most likely an issue in embedded Maven version used in
m2eclipse. We'll be picking up new embedded in a few weeks, so you can try
your project with the command line Maven from trunk and see if it would work
there.
maven 2.0.9 and the embedded maven works fine when doing a package or
install, m2eclipse report this error in maven console log only when I
do project clean.
the maven settings is to use process-test-resources after a clean.
I tried mvn process-test-resources and no problems occurs.
I do the same with embedded maven (via maven build...), no problem again.
Did it appears to other users with others mojo here ?
I could send to Eugene some logs, if you want to see what's differ
between JDT/m2eclipse and regular maven process-test-resources
Regards
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
