You probably want to update your maven version, not the plugin
version... DiagnosisUtils is in the core.
We have an RC of 2.0.2 which will most likely be promoted to the final
release, if you'd like to use that.
It's at:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060113.151503.tar.gz
if you'd like to install that.
One thing I should mention is that this will not allow your build to run
perfectly. There is another error that is being obscured by the error
diagnosis system of Maven...so, if you install a newer version of Maven,
you won't get the error from DiagnosisUtils. BUT you will still see the
*real* error.
HTH,
John
Quenten VanEgeren wrote:
I'm new to Maven2 and this list and I'm having the following problem.
I'm not sure if I'm just missing something, if I have the wrong version
of the surefire plugin, or what.
When I run 'mvn test' I get the following output :
[INFO]task-segment: [test]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 45 source files to
c:\development\maven\common\target\test-classes
[INFO] [surefire:test]
[INFO] Setting reports dir:
c:\development\maven\common\target/surefire-reports
[INFO]
[ERROR] BUILD ERROR
[INFO]
---
constituent[0]: file:/c:/dev/maven-2.0/lib/commons-cli-1.0.jar
constituent[1]:
file:/c:/dev/maven-2.0/lib/doxia-sink-api-1.0-alpha-4.jar
constituent[2]: file:/c:/dev/maven-2.0/lib/jsch-0.1.23.jar
constituent[3]: file:/c:/dev/maven-2.0/lib/maven-artifact-2.0-1.jar
constituent[4]:
file:/c:/dev/maven-2.0/lib/maven-artifact-manager-2.0-1.jar
constituent[5]: file:/c:/dev/maven-2.0/lib/maven-core-2.0.jar
constituent[6]:
file:/c:/dev/maven-2.0/lib/maven-error-diagnostics-2.0.jar
constituent[7]: file:/c:/dev/maven-2.0/lib/maven-model-2.0.jar
constituent[8]: file:/c:/dev/maven-2.0/lib/maven-monitor-2.0.jar
constituent[9]: file:/c:/dev/maven-2.0/lib/maven-plugin-api-2.0.jar
constituent[10]:
file:/c:/dev/maven-2.0/lib/maven-plugin-descriptor-2.0.jar
constituent[11]:
file:/c:/dev/maven-2.0/lib/maven-plugin-parameter-documenter-2.0.jar
constituent[12]:
file:/c:/dev/maven-2.0/lib/maven-plugin-registry-2.0.jar
constituent[13]: file:/c:/dev/maven-2.0/lib/maven-profile-2.0.jar
constituent[14]: file:/c:/dev/maven-2.0/lib/maven-project-2.0-1.jar
constituent[15]: file:/c:/dev/maven-2.0/lib/maven-reporting-api-2.0.jar
constituent[16]:
file:/c:/dev/maven-2.0/lib/maven-repository-metadata-2.0.jar
constituent[17]: file:/c:/dev/maven-2.0/lib/maven-settings-2.0.jar
constituent[18]:
file:/c:/dev/maven-2.0/lib/plexus-interactivity-api-1.0-alpha-4.jar
constituent[19]: file:/c:/dev/maven-2.0/lib/wagon-file-1.0-alpha-5.jar
constituent[20]:
file:/c:/dev/maven-2.0/lib/wagon-http-lightweight-1.0-alpha-5.jar
constituent[21]:
file:/c:/dev/maven-2.0/lib/wagon-provider-api-1.0-alpha-5.jar
constituent[22]: file:/c:/dev/maven-2.0/lib/wagon-ssh-1.0-alpha-5.jar
---
java.lang.NullPointerException
at
org.apache.maven.usability.diagnostics.DiagnosisUtils.appendRootCauseIfPresentAndUnique(DiagnosisUtils.java:89)
at
org.apache.maven.usability.MojoExecutionExceptionDiagnoser.diagnose(MojoExecutionExceptionDiagnoser.java:66)
at
org.apache.maven.usability.diagnostics.ErrorDiagnostics.diagnose(ErrorDiagnostics.java:81)
at
org.apache.maven.DefaultMaven.logDiagnostics(DefaultMaven.java:693)
at org.apache.maven.DefaultMaven.logError(DefaultMaven.java:640)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:119)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Is this being caused by an error coming from one of my tests, or do I
have an old version of one of the plugins?
I ran an 'mvn -U test' and after it updated all of the plugins, I got
the same error.
Thanks for any help you may be able to offer.
Quenten
