You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2005/05/21 16:47:58 UTC

[jira] Closed: (MPCLOVER-32) clover:off does not reset the compiler to javac

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

    Fix Version: 1.9
     Resolution: Fixed
      Assign To: Vincent Massol

Thanks Wim. A patch with some test cases would be just awesome but I guess I can't ask for too much :-) Your information about clover-setup with enabled="false" has helped me a lot. Thanks.

> clover:off does not reset the compiler to javac
> -----------------------------------------------
>
>          Key: MPCLOVER-32
>          URL: http://jira.codehaus.org/browse/MPCLOVER-32
>      Project: maven-clover-plugin
>         Type: Bug
>     Versions: 1.8
>  Environment: maven clover plugin 1.8
> clover version 1.3.5
>     Reporter: Marnix J. van Wendel de Joode
>     Assignee: Vincent Massol
>      Fix For: 1.9

>
>
> I have the problem that when calling clover:off the java compiler is not reset to javac. Any report I run after the clover one in 'maven site' that needs to compile still uses the clover compiler.
> Am I missing something? I see the build.compiler property is reset to an emtpy string (or just removed from the env), but no <ant clover:desetup> is called (since it does not exist).

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org