[ http://jira.codehaus.org/browse/MNG-1327?page=comments#action_49300 ]
Vincent Massol commented on MNG-1327: ------------------------------------- Hi Mark, Have you realized that this parameter is only used by clover:check mojo? If you're doing checks it cannot be 0% as it wouldn't mean anything. I don't understand why it is a problem for you and I certainly won't encourage a default where 0% test coverage will pass a build verified by clover:check :-) When you run the site goal the check is not performed of course! Have you tried using the plugin? I think there's a misundestanding in how it is used (no wonder as there's still no doc yet ;-) I'm working on that but please bear in mind the plugin is not released yet). Thanks > Clover default target percentage too high - should be 0% > -------------------------------------------------------- > > Key: MNG-1327 > URL: http://jira.codehaus.org/browse/MNG-1327 > Project: Maven 2 > Type: Bug > Components: maven-clover-plugin > Versions: 2.0 > Reporter: Mark Kuzmycz > Priority: Trivial > > > The target percentage attribute is a good idea. However, it should be treated > as optional as most projects will want to build irrespective of the target. > This is especially true when you run the site goal. In which case you want > the execution to complete (irrespective of clover restrictions) so that you > can communicate the results to the developers. > Can we please have the default value set to 0% -- 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, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
