[ http://jira.codehaus.org/browse/MCLOVER-39?page=all ]
     
Vincent Massol closed MCLOVER-39:
---------------------------------

    Resolution: Fixed

Done

> clover:check and clover:log should ignore projects with no Clover database 
> rather than error out
> ------------------------------------------------------------------------------------------------
>
>          Key: MCLOVER-39
>          URL: http://jira.codehaus.org/browse/MCLOVER-39
>      Project: Maven 2.x Clover Plugin
>         Type: Bug

>     Versions: 2.1
>  Environment: 2.0.4
>     Reporter: John Allen
>     Assignee: Vincent Massol
>      Fix For: 2.2
>  Attachments: clover-39.patch, clover-profile.txt
>
>
> Either 
> if the project is of a type that is not a java based or if no database is 
> found (potentially qualified with the fact there is no java source present) 
> check should just skip and not error out as it does now
> E.g. checkstyle and pmd do the following:-
> [INFO] [checkstyle:checkstyle]
> [INFO] Source directory does not exist - skipping report.
> [INFO] [checkstyle:check {execution: standards-conformance}]
> [INFO] Unable to perform checkstyle:check, unable to find 
> checkstyle:checkstyle outputFile.
> I note that instrumentInternal is bright enough to not try 
> [INFO] [clover:instrumentInternal]
> [INFO] Not instrumenting sources with Clover as this is not a Java project.
> The current check implementation prevents us from performing multiproject 
> governance enforcing builds from a root POM defined profile.

-- 
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

Reply via email to