Steinhauer, Frank wrote:
I got the same error just some hours ago, using maven 2.0.6 and the surefire-plugin 2.3 . And yes, adding a dependcy to junit solved the problem.
Yup, this is an old bug I remember fixing a while back.
Only thing is, I don't use any unit tests in that project (used only to build a Jboss SAR file), so this behaviour seems a bit strange to me....
According to the old code, the surefirebooter is constructed if:
- the 'test' parameter (-Dmaven.test.skip or from config) is not false, and
- the testclassesdirectory exists, wheter it has testclasses or not.
Testclassesdirectory (target/test-classes) is created by the compiler
plugin, ONLY if the testsourceroot
exists (src/test/java).
So, remove your empty src/test/java/ directory and it's fixed. Or use
the latest 2.3.1 or 2.4 snapshots for surefire.
At least, this is not a problem that's due to maven-2.0.7.
It seems the test phase always requires the junit dependency (I don't call it
explicitly in the POM).
Cheers,
Frank
-----Ursprüngliche Nachricht-----
Von: Kenney Westerhof [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 13. Juni 2007 17:13
An: Maven Developers List
Betreff: Re: [VOTE] Release Maven 2.0.7 - surefire problem
Mark Donszelmann wrote:
Hi Kenney,
Hi Mark,
I was using 2.1.3 for surefire. Changed it to 2.3, and still get error
(slightly different):
Hi,
this is fixed later on; i think you're missing a dependency on junit.
Let me know if this is the case. Can't be due to 2.0.7 though, unless
this works in 2.0.6?
If there's no released version (2.3) that works for 2.0.7 then we need
to release 2.3.1 asap.
-- Kenney
java.lang.NullPointerException
at
org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594)
at
org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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)
My pom (fragment):
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.3</version>
<configuration>
<forkMode>pertest</forkMode>
<includes>
<include>**/*TestSuite.java</include>
</includes>
<excludes>
<exclude>**/TestSuite.java</exclude>
</excludes>
</configuration>
</plugin>
Could not test SNAPSHOTs yet.
Regards
Mark Donszelmann
On Jun 13, 2007, at 6:18 AM, Kenney Westerhof wrote:
Hi,
can you find the surefire plugin version you're using? I've fixed this
problem in the latest snapshots. Only the snapshots were faulty,
latest release should be fine.
If that one is broken too, can you try one of the latest snapshots
(2.4-snapshot
or 2.3.1-snapshot), so we can determine wheter it's a fault in
surefire or in
maven 2.0.7?
Thanks,
Kenney
Mark Donszelmann wrote:
Hi
tried 2.0.7 on FreeHEP, seems to work on most parts, except it tells
me following in one case:
RUN ABORTED
java.lang.LinkageError
org.apache.maven.surefire.Runner
An exception or error caused a run to abort.
Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints
running with -e gives me:
org.apache.maven.lifecycle.LifecycleExecutionException: There are
test failures.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: There are
test failures.
at
org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:389)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
... 16 more
I have seen this error before on 2.0.6 which refrained me from using
it.
2.0.5 works fine though. Any idea?
Do ot let me hold up the release, I am sure it is a config error on
my side, but if you have a hint, let me know.
Regards
Mark Donszelmann
On Jun 12, 2007, at 10:12 PM, Jason van Zyl wrote:
Hi,
The release notes are here:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&styleName=Html&version=13138
The tag is here:
http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.7/
Staging repository:
http://people.apache.org/~jvanzyl/maven-2.0.7-staging-repository/
And the distros you are interested in are here:
http://people.apache.org/~jvanzyl/maven-2.0.7/
Thanks,
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
