You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Ryan H." <wa...@gmail.com> on 2008/04/25 22:31:19 UTC
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Clover 2 plug-in on Maven 2.0.9
Posted by nick pellow <np...@atlassian.com>.
Hi Brian,
I raised this JIRA regarding the issue you are seeing:
http://jira.codehaus.org/browse/MNG-3530 .
Clover uses a forked lifecycle, and sets the oputput directory and the work
directory to target/clover/ .
See the source here:
http://svn.atlassian.com/fisheye/browse/public/contrib/clover/maven-clover-plugin/trunk/src/main/java/com/atlassian/maven/plugin/clover/CloverInstrumentInternalMojo.java?r=17316#l199
.
Since 2.0.9, Maven resolves all properties before the lifecycle is forked,
as can be seen in the sample project I attached to the above JIRA. This
means that by the time the Clover plugin sees the properties, they can no
longer be resolved relative to the clover directory.
Is this really expected behaviour in Maven 2.0.9?
I would think that any plugin which uses a forked lifecycle would be
affected in the same way.
Cheers,
Nick Pellow
Clover Tech Lead.
Brian E Fox wrote:
>
> 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:waycool88@gmail.com]
> 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 <br...@reply.infinity.nu>
> 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:waycool88@gmail.com]
>> 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: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Clover-2-plug-in-on-Maven-2.0.9-tp16905121s177p16930307.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Clover 2 plug-in on Maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:waycool88@gmail.com]
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 <br...@reply.infinity.nu>
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:waycool88@gmail.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Clover 2 plug-in on Maven 2.0.9
Posted by "Ryan H." <wa...@gmail.com>.
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 <br...@reply.infinity.nu> 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:waycool88@gmail.com]
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Clover 2 plug-in on Maven 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
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:waycool88@gmail.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org