I've managed to create an eclipse project by running "mvn
eclipse:eclipse" in the maven-2.0.4 source tree. And after defining the
M2_REPO classpath variable, I was able to get Eclipse to not show any
errors when building. In setting up for debugging, I use the command
line parameters:
-Dclassworlds.conf=/opt/maven-2.0.4/bin/m2.conf
-Dmaven.home=/opt/maven-2.0.4
When I run, I get the error:
java.lang.Exception: classworlds configuration not specified nor found
in the classpath
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:423)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Now, I believe I *am* specifying the classworlds config path correctly
(see above command line parameter). I can't seem to find the source for
classworlds (I can browse the cvs repository and download individual
files from this package, but I can't find a source jar file to
download).
Anyone know what is going on? Anyone know where I can download the
source to classworlds so I can debug into Launcher to see why it doesn't
think it can find a conf file? Thanks. -- Eric
________________________________
From: Swenson, Eric
Sent: Thursday, October 12, 2006 9:18 PM
To: 'Maven Developers List'
Subject: debugging maven with eclipse
Can anyone point me to instructions on how to use eclipse to debug
maven? I'm having a problem that no one, so far, has commented on -
namely that when I do a reactor build of my project (top-level with
sub-projects), I get the error (when doing "mvn install"):
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-jar-plugin:2.1:jar': Unable to find the
mojo 'org.apache.maven.plugins:maven-jar-plugin:2.1:jar' in the plugin
'org.apache.maven.plugins:maven-jar-plugin'
But when I go to each subdirectory in the project and do a "mvn
install", they all complete successfully. Only when I try to run from
the parent directory do I have this problem. Running with the -X -e
options doesn't give me anything useful.
Is there an easy way to produce an eclipse project from the maven2
source tree? Or do I have to manually all all the "src" directories in
a new project? I'd like to run under the debugger and step through the
execution to pinpoint the issue. Thanks. -- Eric
