[jira] Commented: (MPCLOVER-30) clover:on does not see updated maven.compile.src.set

["Vincent Massol (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MPCLOVER-30?page=comments#action_39480 ]
     
Vincent Massol commented on MPCLOVER-30:
----------------------------------------

Thanks Eric. You should not call clover:on twice. This will lead to unexpected results as it's not a valid use case. You should always call clover:off after calling clover:on.

I'd suggest to add your generated source dir to the maven.compile.src.set ref first and then only call clover:on.



> clover:on does not see updated maven.compile.src.set
> ----------------------------------------------------
>
>          Key: MPCLOVER-30
>          URL: http://jira.codehaus.org/browse/MPCLOVER-30
>      Project: maven-clover-plugin
>         Type: Bug
>     Versions: 1.7
>     Reporter: Eric Lapierre
>     Priority: Minor
>  Attachments: plugin.jelly.patch, project.xip
>
>
> In our environment, we do generate some source code, so when we 
> invoke clover:on, the code does not already exist, so the fileset does not contain our code.
> So we are now calling clover:on whenever we generate some source code.
> This is done after the maven.compile.src.set is modified. The problem is at the second invocation of clover:on,  the clover:on goal does not see the new value of maven.compile.src.set.
> It looks like ant:pathconvert, does not override a property if it is already set.

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