[ http://jira.codehaus.org/browse/MOJO-271?page=comments#action_57792 ]
Mike Perham commented on MOJO-271:
----------------------------------
Brett, with your revert I get the following exception. Note [surefire:test]
being printed twice. What would cause surefire to be run twice? I'm using
surefire-plugin 2.1.2.
[INFO] [surefire:test]
[INFO] Setting reports dir:
D:\perforce\depot\modules\cordoba\client\api\target/surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Cobertura: Loaded information on 60 classes.
0 WARN ehcache.config.Configurator - No configuration found. Configuring
ehcache from ehcache-
failsafe.xml found in the classpath: jar:file:/C:/Documents and
Settings/mperham.WEBIFY/.m2/reposito
ry/ehcache/ehcache/1.1/ehcache-1.1.jar!/ehcache-failsafe.xml
485 WARN hibernate.cache.EhCacheProvider - Could not find configuration
[com.webify.framework.tr
iples.beans.NamespaceBean]; using defaults.
[surefire] Running com.webify.wsf.client.ClientTestSuite
[surefire] Tests run: 56, Failures: 0, Errors: 0, Time elapsed: 18.114 sec
[surefire]
Results :
[surefire] Tests run: 56, Failures: 0, Errors: 0
[INFO] [surefire:test]
[INFO] Setting reports dir:
D:\perforce\depot\modules\cordoba\client\api\target/surefire-reports
[INFO]
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] There are some test failure.
[INFO]
----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: There are some test
failure.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:859)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:731)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:502)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:485)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:455)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java
:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
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:324)
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 some test
failure.
at org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:384)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
... 20 more
> Cobertura runs tests twice
> --------------------------
>
> Key: MOJO-271
> URL: http://jira.codehaus.org/browse/MOJO-271
> Project: Mojo
> Type: Bug
> Components: cobertura
> Versions: 2.0-beta-1
> Reporter: Mike Perham
> Fix For: 2.0-beta-1
>
>
> The lifecycle.xml specifies a test goal but apparently this is redundant and
> the second execution immediately fails the build. The standard forked
> lifecycle already contains a test goal. If I just comment the entire block
> out, it works as expected.
--
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