You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Allen (JIRA)" <ji...@codehaus.org> on 2006/05/17 14:48:40 UTC
[jira] Created: (MCLOVER-39) check should skip projects that are
not applicable rather than error out
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
[jira] Commented: (MCLOVER-39) check should skip projects that are
not applicable rather than error out
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MCLOVER-39) clover:check and clover:log should
ignore projects with no Clover database rather than error out
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-39?page=all ]
Vincent Massol updated MCLOVER-39:
----------------------------------
Attachment: clover-39.patch
> 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
[jira] Updated: (MCLOVER-39) clover:check and clover:log should
ignore projects with no Clover database rather than error out
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-39?page=all ]
Vincent Massol updated MCLOVER-39:
----------------------------------
Fix Version: 2.2
Summary: clover:check and clover:log should ignore projects with no Clover database rather than error out (was: clover:check should skip projects that are not applicable rather than error out)
> 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-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
[jira] Commented: (MCLOVER-39) check should skip projects that are
not applicable rather than error out
Posted by "John Allen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-39?page=comments#action_65516 ]
John Allen commented on MCLOVER-39:
-----------------------------------
multiproject environment
top level POM project declares a profile that sets up some governance checking build goals (pmd, checkstyle, clover)
second level contains POM and JAR projects
third-level contains POM and JARs
forth level contains JAR projects
see attachment for details of profile
build runs, clover:instrument skips POM projects, clover:check does not and fails with "can not find clover database".
> 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
> Assignee: Vincent Massol
>
>
> 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
[jira] Updated: (MCLOVER-39) clover:check should skip projects that
are not applicable rather than error out
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-39?page=all ]
Vincent Massol updated MCLOVER-39:
----------------------------------
Summary: clover:check should skip projects that are not applicable rather than error out (was: check should skip projects that are not applicable rather than error out)
> clover: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
> Assignee: Vincent Massol
> Attachments: 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
[jira] Closed: (MCLOVER-39) clover:check and clover:log should
ignore projects with no Clover database rather than error out
Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MCLOVER-39) check should skip projects that are
not applicable rather than error out
Posted by "John Allen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCLOVER-39?page=all ]
John Allen updated MCLOVER-39:
------------------------------
Attachment: clover-profile.txt
> 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
> Assignee: Vincent Massol
> Attachments: 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