|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
- [mojo-dev] [jira] (MCOBERTURA-78) have the maven site show a cobertur... JIRA
In this case, I agree with Benson.
It may be relevant to see a cobertura sample report from another project in the project documentation, as is currently done.
Adding a Cobertura report of the plugin project itself adds unnecessary complexity, since we have only 2 bad options to do it:
Besides, since a plugin quite heavily relies upon Integration Tests for its full testing (as opposed to only unit tests), the setup
of Cobertura in this aggregate way is extremely complex to say the least. A simpler way is to include a sample report, as is done.