Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MPCLOVER-23 Here is an overview of the issue: --------------------------------------------------------------------- Key: MPCLOVER-23 Summary: clover plugin doesn't reset compiler Type: Bug Status: Unassigned Priority: Major Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven-clover-plugin Versions: 1.6 Assignee: Reporter: fabrizio giustina Created: Sun, 26 Sep 2004 10:06 AM Updated: Sun, 26 Sep 2004 10:06 AM Description: when running clover:clover (1.6 SNAPSHOT) I end up with the clover compiler set as the standard build.compiler (clover will be used to compile classes also after the report generation). looking at the goals executed I can see: clover=clover:test,clover:report clover:test clover:init clover:on -> clover compiler ... clover:off -> standard compiler clover:report clover:init clover:on -> clover compiler again ... > end (without clover:off) this probably happens because clover:report still has "clover:on" as a prerequisite. Clover:on is used to set the clover compiler but afaik this is not needed for the report generation. Replacing clover:on with clover:init fix this behaviour. FIX In plugin.jelly replace: <goal name="clover:report" prereqs="clover:on" with: <goal name="clover:report" prereqs="clover:init" --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
