[ 
http://jira.codehaus.org/browse/MCOBERTURA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104735
 ] 

Paul Phillips commented on MCOBERTURA-25:
-----------------------------------------

I am also getting this error with maven 2.0.7 and maven-surefire-plugin 2.3 
running with cobertura-maven-plugin 2.1.  The cobertura-check.bat reports 
correctly the contents of the cobertura.ser file.

Any idea what may be causing this issue or how to get around it without 
building the site twice - as this will double an already quite long build time.

> 0% Code coverage reported
> -------------------------
>
>                 Key: MCOBERTURA-25
>                 URL: http://jira.codehaus.org/browse/MCOBERTURA-25
>             Project: Maven 2.x Cobertura Plugin
>          Issue Type: Bug
>         Environment: Maven 2.0.3. 
> cobertura-maven-plugin-2.0-20060331.055400-6
> surefire 2.2-SNAPSHOT
>            Reporter: Adrian
>            Assignee: Brett Porter
>            Priority: Critical
>
> I have an EJB 3 project that runs JUnit tests by invoking a JUnit TestSuite 
> that starts up the JBoss EJB 3 embeddable, runs the unit tests in the 
> container, shuts down the container.
> I explicitly deploy the cobertura instrumented classes to the EJB 3 container.
> When cobertura produces its report, it reports that there is 0% code 
> coverage. All the unit tests run correctly and pass. The generated 
> cobertura.ser file is created in the base directory of the project. No stack 
> traces or errors appear in mavens output. I am running 
> {code}
> mvn clean cobertura:clean cobertura:cobertura
> {code}
> If I take the generated cobertura.ser file, download [cobertura 
> 1.7|http://cobertura.sourceforge.net/] and run {{cobertura-report.sh}} script 
> against the cobertura.ser I get the correct code coverage report.
> *So, something is going wrong when the report is running, since the ser file 
> is correct when run with cobertura at command line.*
> _Unfortunately I cannot attach a test case as we had to manually add lots of 
> EJB 3 embeddable jars to our repo that are not available on ibiblio. So any 
> test case I would upload would not build._ :-(
> If you require any further information I can provide it.

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

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to