Hi there. I've seen some references to the problems I'm having,
including some bug reports, but I haven't found any solutions. Maybe
somebody can point me in the right direction.
About my install: I'm using eclipse for JEE for Windows, downloaded in
the past few days from eclipse.org. I installed m2eclipse from the dev
update site today.
First, I'm trying to use an external maven, but the maven builder always
uses the embedded version, which seems to be the root cause of all of
these problems. When I run maven builds with the "Run As" menu (which
uses my external version properly), things seem to work fine. I've
found that both maven 2.0.9 and maven 2.1.0-M1 build my projects just
fine from the command line.
I guess the question I have is this -- is there a way to either update
the embedded maven to one that works properly or force the maven builder
to use the externally configured maven?
So now, on to the specific issues:
1) I get the following message in the maven console related to
the maven-cobertura plugin
1/15/09 2:12:03 PM EST: Build errors for WorkflowRouter-mule;
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
construct build plan for: Mule Service Container
Id: org.oclc.WorkflowRouter:WorkflowRouter-mule:jar:1.0-SNAPSHOT
task-segment: [process-test-resources]. Reason: Mojo descriptor:
cobertura:instrument doesn't have a default lifecycle phase. Please
specify a <phase/> for this goal in your POM.
I found this
http://www.nabble.com/m2eclipse%27s-build-problem---pmd:cpd-doesn%27t-ha
ve-a-default-lifecycle-phase-td19329122.html, but since the builder
itself doesn't seem to use my external installation, the suggested
workaround doesn't help me.
2) If I remove cobertura from my pom, I get the following
message about a problem with the maven-enforcer plugin, which I see is a
known issue (http://jira.codehaus.org/browse/MNGECLIPSE-1091). Is there
a workaround of any kind?
1/15/09 2:20:35 PM EST: Build errors for WorkflowRouter-core;
org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or
missing parameters: [Mojo parameter [name: 'rules'; alias: 'null']] for
mojo: org.apache.maven.plugins:maven-enforcer-plugin:1.0-alpha-3:enforce
3) If I remove the maven-enforcer plugin from my pom, I still
have an issue with the gmaven plugin. Part of the message I get is
below (the listing of jar files is elided).
1/15/09 2:21:31 PM EST: [INFO] [groovy:generateStubs]
1/15/09 2:21:31 PM EST: [FATAL ERROR]
org.codehaus.groovy.maven.plugin.stubgen.GenerateStubsMojo#execute()
caused a linkage error (java.lang.NoSuchMethodError). Check the realms:
NOTE:
Plugin realm is:
/plugins/org.codehaus.groovy.maven:gmaven-plugin:1.0-r...@48/thread:Work
er-10
Container realm is: plexus.core
....
I found this (http://jira.codehaus.org/browse/MGROOVY-144), which
suggested using 1.0-rc4-SNAPSHOT. If I try that, unfortunately, I get
the following message:
1/15/09 2:24:36 PM EST: Build errors for WorkflowRouter-mule;
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error
in the plugin manager executing goal
'org.codehaus.groovy.maven:gmaven-plugin:1.0-rc-4-SNAPSHOT:compile':
Mojo execution failed.
Google can't find me anything on this error, so I'm stumped. I've tried
setting some config flags for the gmaven plugin in the pom to get more
details, but no luck.
