I agree it's probably 2.0.9...I was speculating on what the exact edge
case here is and I'm betting its that Clover is trying to change that
folder, or is causing the folder to change and the property isn't
reflecting it.

-----Original Message-----
From: Ryan H. [mailto:[EMAIL PROTECTED] 
Sent: Saturday, April 26, 2008 6:44 PM
To: Maven Users List
Subject: Re: Clover 2 plug-in on Maven 2.0.9

with Maven 2.0.7, the property is set to
c:\mytest\myproject\target\clover when under Clover run because Clover
maven 2 plug-in is instrumenting code under that directory. However,
it doesn't work anymore under Maven 2.0.9. To me, it sounds like a bug
in 2.0.9. Otherwise, we would've examined all of existing plug-ins
whenever there is new Maven release.

On Sat, Apr 26, 2008 at 6:21 AM, Brian E. Fox <[EMAIL PROTECTED]>
wrote:
> Someone else reported issues with that property in 2.0.9 so it could
be
> maven. ${project.buid.directory} should be c:\mytest\myproject\target
> but maybe the problem is with clover trying to change it?
>
>
> -----Original Message-----
> From: Ryan H. [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 25, 2008 4:31 PM
> To: Maven Users List
> Subject: Clover 2 plug-in on Maven 2.0.9
>
> Folks,
>
> I just found that Maven 2.0.9 does not work with the existing Clover 2
> maven 2 plug-in (group ID: com.atlassian.maven.plugins) if you are
> using some of maven 2 properties specifying project directories such
> as ${project.build.directory} etc.
>
> You can use maven's antrun plug-in to echo out this property under
Maven
> 2.0.7 and 2.0.9 when running "clover:instrument" goal. Under Maven
> 2.0.7, ${project.build.directory} prints:
>
>   c:\mytest\myproject\target/clover
>
> Whereas Maven 2.0.9 prints:
>
>   c:\mytest\myproject\target
>
>
> Has anyone used Clover 2 plug-in on Maven 2.0.9 successfully? Is it a
> bug in Maven 2.0.9 or Clover 2 plugin?
>
> Thanks
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to