[ http://jira.codehaus.org/browse/MCLOVER-50?page=comments#action_73027 ] Vincent Massol commented on MCLOVER-50: ---------------------------------------
Hi Andrew, Yes this would be a nice feature but the problem is that it means the Clover plugin needs to know all the plugins that can fail. The surefire plugin is only one plugin but there are other plugins that fail the build in case of errors. For example checkstyle, PMD, etc can fail the build in case of violations. Anyone can develop a custom testing plugin too. It's not possible for the clover plugin to know about all plugins that can exist. Thus the only real solution would be for Maven core to have a flag to tell not to stop the build till the end. Feel free to create a JIRA issue for this or discuss it on the Maven list. Let me know if you have some ideas. Thanks -Vincent > Test failure during Site goal should not stop the Clover build > -------------------------------------------------------------- > > Key: MCLOVER-50 > URL: http://jira.codehaus.org/browse/MCLOVER-50 > Project: Maven 2.x Clover Plugin > Issue Type: Bug > Affects Versions: 2.2 > Reporter: Andrew Perepelytsya > Assigned To: Vincent Massol > Priority: Critical > > This problem is similar to whatever surefire-report plugin experienced up > until recently. Clover plugin runs tests in its own lifecycle. If there was a > test failure, the build should continue and site be generated with failure > reports. At the moment the build is stopped with a failure completely, and > site *not* generated. -- 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
