[ http://jira.codehaus.org/browse/MPCLOVER-32?page=comments#action_31485 ]
Wim Deblauwe commented on MPCLOVER-32:
--------------------------------------
clover:off needs to disable the clover compiler like this:
<ant:clover-setup
initstring="${maven.clover.database}"
flushpolicy="interval"
flushinterval="500"
enabled="false"/>
There is however a pitfall to this:
Calling 'maven clover:on jar clover:off jar' will produce a clovered jar! That
is because maven/ant sees that the classes are already compiled. You need to do
a clean in between.
I use this to generate a nightly build with a website with Clover, but have a
"clean" jar deployed at our server repository.
> 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
>
>
> 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
-
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]
