[ http://jira.codehaus.org/browse/MCOBERTURA-1?page=comments#action_62186 ] 

Nigel Magnay commented on MCOBERTURA-1:
---------------------------------------

Aha

Closer examination shows this is due to a bug in surefire-booter-1.5.2, which 
looks like it is fixed in trunk.

Can a new version of surefire-booter be released to fix this ?


> When using cobertura, build fails believing tests have failed when they 
> haven't
> -------------------------------------------------------------------------------
>
>          Key: MCOBERTURA-1
>          URL: http://jira.codehaus.org/browse/MCOBERTURA-1
>      Project: Maven 2.x Cobertura Plugin
>         Type: Bug

>  Environment: Maven 2.0.2
> Cobertura built from latest SVN
>     Reporter: Nigel Magnay
>     Priority: Minor
>      Fix For: 2.0

>
>
> Project builds correctly, and surefire:test executes with 0 errors
> POM is setup to include cobertura:
> <build>
>               <plugins>
>                 <plugin>
>         <groupId>org.codehaus.mojo</groupId>
>         <artifactId>cobertura-maven-plugin</artifactId>
>         <executions>
>           <execution>
>             <goals>
>               <goal>clean</goal>
>             </goals>
>           </execution>
>         </executions>
>       </plugin>
>               </plugins>
>               </build>
> When running cobertura:cobertura, build proceeds correctly, and the tests all 
> run correctly, but then the build fails:
> Results :
> [surefire] Tests run: 10, Failures: 0, Errors: 0
> [WARNING] POM for 'kernel:framework:pom:1.0(8)' is invalid. It will be 
> ignored f
> or artifact resolution. Reason: Not a v4.0.0 POM.
> [INFO] [surefire:test]
> [INFO] Setting reports dir: W:\1244 - Knowledge Management System 
> (KMS)\dev\modu
> les\kms-services\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 
> fail
> ure.
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:556)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:472)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecy
> cle(DefaultLifecycleExecutor.java:859)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(Def
> aultLifecycleExecutor.java:731)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:502)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> Goal(DefaultLifecycleExecutor.java:485)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:455)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:303)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:270)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.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(DelegatingMethodAcces
> sorImpl.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 some 
> test f
> ailure.
>         at 
> org.apache.maven.test.SurefirePlugin.execute(SurefirePlugin.java:384)
>         at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:415)
>         at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:531)
>         ... 20 more
> [INFO] 
> -------------------------------------------------------------------------
> ---
> [INFO] Total time: 32 seconds
> [INFO] Finished at: Tue Feb 21 11:30:27 GMT 2006
> [INFO] Final Memory: 18M/83M
> [INFO] 
> -------------------------------------------------------------------------

-- 
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

Reply via email to