[ http://jira.codehaus.org/browse/MPCLOVER-30?page=all ]
Vincent Massol closed MPCLOVER-30:
----------------------------------
Fix Version: 1.10
Resolution: Fixed
Assign To: Vincent Massol
Applied thanks. I have applied it in clover:off rather than clover:on because
clover:off must be called before calling clover:on again. Let me know if it
works for you.
> 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
> Assignee: Vincent Massol
> Priority: Minor
> Fix For: 1.10
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
