[ http://jira.codehaus.org/browse/MCLOVER-39?page=comments#action_65515 ]
Vincent Massol commented on MCLOVER-39: --------------------------------------- Hi John, Could you describe what goals you are calling as there are several ways to run the clover plugin? Could you also show the console error you're getting and provide more information about the project where this errors out? Thanks > check should skip projects that are not applicable 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 > > > 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
