[ http://jira.codehaus.org/browse/MCOBERTURA-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250278#action_250278 ]
Harald Brabenetz commented on MCOBERTURA-86: -------------------------------------------- I use the following workaround: {noformat} <profile> <!-- Build with IntegrationTestcoverage => instrument classes with cobertura before integrationtests starts. --> <id>buildWithIntegrationTestCoverage</id> <activation> <property> <name>buildWithIntegrationTestCoverage</name> <value>true</value> </property> </activation> <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> <version>2.3</version> <executions> <execution> <id>instrument-classes</id> <phase>package</phase> <goals> <goal>instrument</goal> </goals> </execution> </executions> </plugin> <!-- Add cobertura as dependency to the jetty-plugin (required for instrumented classes) --> <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <dependencies> <dependency> <groupId>org.codehaus.mojo</groupId> <artifactId>cobertura-maven-plugin</artifactId> <version>2.3</version> <type>jar</type> </dependency> </dependencies> </plugin> </plugins> </build> </profile> {noformat} And then i start the site-generation with: {noformat} mvn clean install site -DbuildWithIntegrationTestCoverage=true {noformat} > no coverage reported for integration-test > ----------------------------------------- > > Key: MCOBERTURA-86 > URL: http://jira.codehaus.org/browse/MCOBERTURA-86 > Project: Maven 2.x Cobertura Plugin > Issue Type: Bug > Affects Versions: 2.2 > Environment: Windows XP, maven 2.0.8 > Reporter: Jean-Francois Poilpret > Attachments: > cobertura-maven-plugin_check-only-and-report-only-mojos_with-IT.patch, > cobertura-maven-plugin_check-only-and-report-only-mojos_with-IT_for-2.5-SNAPSHOT.patch, > cobertura-maven-plugin_check-only-mojo.patch, > CoberturaIntegrationReportMojo.patch, CoberturaReportOnlyMojo.patch > > > In my project, I have both unit tests ("test" phase) and integration tests > ("integration-test" phase). > So far I could manage configuring maven-surefire-plugin and > maven-surefire-report-plugin to execute both tests correctly and also > generate 2 different reports. > Then I have added cobertura-maven-plugin to the reporting in order to get > coverage but unfortunately only unit tests have their coverage reported (I > know it because I have some classes which are only integration tested but are > reported as 0% covered). > After trying to find information on the mailing lists, on the web and other > existing resources, I could not find any hint on how to make this work. > It looks like cobertura-maven-plugin, by its current design, will never run > integration-test to collect coverage, it seems to stop at the "test" phase. > Thus whenever a POM project has integration tests and uses > cobertura-maven-plugin for coverage report, the generated reports are wrong, > which is very misleading. > Actually, I was surprised not to find this issue already in JIRA. > Is there a chance this gets fixed soon? Or is there a usable workaround for > this problem (besides switching to clover which I am not sure it would work > better ;-)) Did someone succeed in patching cobertura-maven-plugin to get the > correct behavior? -- 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