NullPointerException when running DotnetTestMojo indepentely
------------------------------------------------------------
Key: NMAVEN-141
URL: http://jira.codehaus.org/browse/NMAVEN-141
Project: NMaven
Issue Type: Bug
Affects Versions: 0.16
Environment: Windows, JDK 1.6, Maven 2.0.9
Reporter: Erik Mattsson
Steps to reproduce
1. Go to a project with NUnit tests
2. run "mvn org.apache.maven.dotnet.plugins:maven-dotnet-test-plugin:test"
Expected outcome:
NUnit runs the tests
Actual outcome:
NPE exception:
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Class Library
[INFO] task-segment:
[org.apache.maven.dotnet.plugins:maven-dotnet-test-plugin:test]
[INFO] ------------------------------------------------------------------------
[INFO] [dotnet-test:test]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.dotnet.plugin.nunit.DotnetTestMojo.getTestAssemblyName(DotnetTestMojo.java:158)
at
org.apache.maven.dotnet.plugin.nunit.DotnetTestMojo.execute(DotnetTestMojo.java:86)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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:597)
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)
--
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
