Maven 2.x Cobertura Plugin

have the maven site show a cobertura report

Details

  • Type: Improvement Improvement
  • Status: Reopened Reopened
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Along the lines of eating your own dog food (as the expression goes), it would be great if the plugin site [1] had the coverage report configured as per the usage [2].

[1] http://mojo.codehaus.org/cobertura-maven-plugin/project-reports.html
[2] http://mojo.codehaus.org/cobertura-maven-plugin/usage.html

It could be the latest stable version, but that would be neat if it used the current version.

Activity

Hide
Arnaud Heritier added a comment -

Done

Show
Arnaud Heritier added a comment - Done
Hide
Arnaud Heritier added a comment -

Won't fix

Show
Arnaud Heritier added a comment - Won't fix
Hide
Arnaud Heritier added a comment -

I removed it because the report generates always 0% on our code.
It's certainly due to plexus.
I'm not sure that it can be fixed

Show
Arnaud Heritier added a comment - I removed it because the report generates always 0% on our code. It's certainly due to plexus. I'm not sure that it can be fixed
Hide
Jim Sellers added a comment -

I've had to lock down to version 2.0. Does that work for you?

Show
Jim Sellers added a comment - I've had to lock down to version 2.0. Does that work for you?
Hide
Arnaud Heritier added a comment -

Comment I didn't try, but if it works with 2.0 and not 2.2-SNAPSHOT we have a problem

Show
Arnaud Heritier added a comment - Comment I didn't try, but if it works with 2.0 and not 2.2-SNAPSHOT we have a problem
Hide
Jim Sellers added a comment -

I could never get 2.1 to work. It always reported 100% coverage on classes hit by ANY tests and didn't show classes that had 0% coverage.

Show
Jim Sellers added a comment - I could never get 2.1 to work. It always reported 100% coverage on classes hit by ANY tests and didn't show classes that had 0% coverage.
Hide
Arnaud Heritier added a comment -

Did you try the 2.2-SNAPSHOT ??

Show
Arnaud Heritier added a comment - Did you try the 2.2-SNAPSHOT ??
Hide
Jim Sellers added a comment -

The issue we had found with 2.1 seems to have been reported MCOBERTURA-66. I thought that it had been reported before that. 2.2 wasn't being worked on when we ran into our issues.

Either way, I think that we're getting off track here. If the plugin cannot report coverage on itself then there's a problem. "It's certainly due to plexus."??? Is this a know issue / bug with the plugin? Is this documented somewhere?

When you tried, did you try against 2.2-SNAPSHOT or did it just pick up the latest "stable" version?

Thank you for taking the time and working on this.

Show
Jim Sellers added a comment - The issue we had found with 2.1 seems to have been reported MCOBERTURA-66. I thought that it had been reported before that. 2.2 wasn't being worked on when we ran into our issues. Either way, I think that we're getting off track here. If the plugin cannot report coverage on itself then there's a problem. "It's certainly due to plexus."??? Is this a know issue / bug with the plugin? Is this documented somewhere? When you tried, did you try against 2.2-SNAPSHOT or did it just pick up the latest "stable" version? Thank you for taking the time and working on this.
Hide
Arnaud Heritier added a comment -

I tried with the latest 2.2-SNAPSHOT.
The problem is that I don't have enought skills in corbertura to understand why it fails on this plugin.
I don't see any interesting traces even if i launch it in debug mode.
The vote to release the 2.2 is already launched

Show
Arnaud Heritier added a comment - I tried with the latest 2.2-SNAPSHOT. The problem is that I don't have enought skills in corbertura to understand why it fails on this plugin. I don't see any interesting traces even if i launch it in debug mode. The vote to release the 2.2 is already launched
Hide
Benson Margulies added a comment -

I don't see why this matters. Absent more comments or someone else willing to work on this, I plan to close this issue post-2.5 and delete the report from the site. If cobertura doesn't get along with complex maven / plexus class loaders we're not going to be able to fix it in the plugin.

Show
Benson Margulies added a comment - I don't see why this matters. Absent more comments or someone else willing to work on this, I plan to close this issue post-2.5 and delete the report from the site. If cobertura doesn't get along with complex maven / plexus class loaders we're not going to be able to fix it in the plugin.
Hide
Robert Scholte added a comment -

I think this one should stay open. It's about the code-coverage of a plugin, which is a good thing to report. Maybe we can contact Kristian Rosenveld, he had a similar problem: how to test the surefire-plugin with the surefire-plugin? He could come up with some ideas.

Show
Robert Scholte added a comment - I think this one should stay open. It's about the code-coverage of a plugin, which is a good thing to report. Maybe we can contact Kristian Rosenveld, he had a similar problem: how to test the surefire-plugin with the surefire-plugin? He could come up with some ideas.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated: