maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Perepelytsya (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MCLOVER-50) Test failure during Site goal should not stop the Clover build
Date Tue, 22 Aug 2006 14:22:48 GMT
    [ http://jira.codehaus.org/browse/MCLOVER-50?page=comments#action_73030 ] 
            
Andrew Perepelytsya commented on MCLOVER-50:
--------------------------------------------

Vincent,

Thanks for taking a look. I think site goal is very different from, e.g. install. Does it
make sense to ignore all failures during site generation then? The interesting point Cobertura
plugin does work as requested even with test failures, maybe there's some interesting stuff
in their code?

Anyway, that is the only thing stopping us from using Clover plugin, though I like those polished
coverage reports it produces.

> 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

        

Mime
View raw message