Shouldn't this be sent to [EMAIL PROTECTED]
- Brett
Vincent Massol wrote:
> The Clover plugin for m2 has been released. It should be available on
> ibiblio in a few hours.
>
> Release Notes - Maven 2.x Clover Plugin - Version 2.1
>
> ** Bug
> * [MCLOVER-7] - "mvn clover:report" generates er
The Clover plugin for m2 has been released. It should be available on
ibiblio in a few hours.
Release Notes - Maven 2.x Clover Plugin - Version 2.1
** Bug
* [MCLOVER-7] - "mvn clover:report" generates errors in tests that
execute properly in "mvn test"
* [MCLOVER-16]
The Clover plugin for Maven2 v2.0 has been released.
Documentation can be found at:
http://maven.apache.org/plugins/maven-clover-plugin/
Some usage examples can be found at: http://tinyurl.com/atax2
Current features:
* Generate Clover reports (clover:clover)
* Ability to fail the build if the
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: jeudi 27 octobre 2005 01:31
> To: 'Maven Developers List'
> Subject: RE: [m2] Clover plugin issue with latest install plugin
>
>
>
> > -Original Message---
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 26 octobre 2005 07:46
> To: Maven Developers List
> Subject: Re: [m2] Clover plugin issue with latest install plugin
>
> It is supposed to clone the lifecycle, and the clover plugi
It is supposed to clone the lifecycle, and the clover plugin used to
work. Bug?
- Brett
Vincent Massol wrote:
Hi there,
The Clover plugin forks a custom lifecycle when executing either the
clover:check or clover:clover mojo. Let's take the clover:check mojo as an
example:
@phase verify
@exec
Hi there,
The Clover plugin forks a custom lifecycle when executing either the
clover:check or clover:clover mojo. Let's take the clover:check mojo as an
example:
@phase verify
@execute phase="test" lifecycle="clover"
Thus, if the user calls "mvn install" on a project where the clover:check
mojo
Vincent Massol wrote:
I'm not saying option 2 should be chosen. I'd just like to quickly explore
this possibility as we have discussed the design for option 1 so far and
we've not talked about this option 2.
I believe this is already possible with the current setup of profiles
and the lifecy
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 16 juin 2005 15:27
> To: Maven Developers List
> Subject: Re: [m2] Clover plugin use cases (was RE: [m2] "Verification"
> phase required?)
[snip]
> >Alternatively we
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 16 juin 2005 15:27
> To: Maven Developers List
> Subject: Re: [m2] Clover plugin use cases (was RE: [m2] "Verification"
> phase required?)
[snip]
> >Alternatively we
Vincent Massol wrote:
BTW, is there a Java API to programmatically call a goal/phase?
Not presently. I'm not sure we want to go down the attainGoal path
again, but there may be a case (eg, the release plugin currently
executes m2 outright - that's more like maven:maven than attainGoal
tho
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mardi 14 juin 2005 07:58
> To: Maven Developers List
> Subject: Re: [m2] Clover plugin use cases (was RE: [m2] "Verification"
> phase required?)
[snip]
> >It's a test s
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mardi 14 juin 2005 07:58
> To: Maven Developers List
> Subject: Re: [m2] Clover plugin use cases (was RE: [m2] "Verification"
> phase required?)
[snip]
> >It's a test s
Ok, responses inline.
Vincent Massol wrote:
It's a test so I guess it's "normal" you may wish to run it in the "release"
lifecycle as part of "m2 install".
We don't actually have a release lifecycle, so we need to think about
how this applies. I would like to keep it a little separate thoug
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: lundi 13 juin 2005 02:05
> To: Maven Developers List
> Subject: Re: [m2] "Verification" phase required?
>
> Are you now doing these checks as part of a normal "m2 install" build?
Yes
> That is probably a bit he
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: dimanche 17 avril 2005 16:45
> To: 'Maven Developers List'
> Subject: RE: [M2] clover
[snip]
> Also, there's something I'm not sure I understand. Where do you tell m2
>
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: dimanche 17 avril 2005 15:23
> To: dev@maven.apache.org
> Subject: Re: [M2] clover
[snip]
> #project.build.directory instead of #basedir/target
Makes sense. (If you want to fix it, I
(sorry for mashing these together, my email client decided to download
and make them vanish, so I've pulled these from a digest request)
>Funny that you should say this when I've been unable to find a single unit
>test in all the plugins that currently exist for m2! :-)
>
>
Yes, this is true. So
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: dimanche 17 avril 2005 04:34
> To: Maven Developers List
> Subject: Re: [M2] Clover plugin ideas and questions
>
> I remember I was going to reply to this :)
>
> Vincent Massol wrote:
I remember I was going to reply to this :)
Vincent Massol wrote:
>Hi,
>
>2/ Option 2: Generate instrumented sources in target/ somewhere and somehow
>convince the compile plugin to use those sources rather than the ones in
>src/main/java.
>
>
I'd definitely say 2. I don't like the clover:on com
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: mercredi 13 avril 2005 11:44
> To: Maven Developers List
> Subject: RE: [M2] Clover plugin ideas and questions
[snip]
> ?? I always had the impression, Clover instruments the class fil
Hi Vincent,
Vincent Massol wrote on Wednesday, April 13, 2005 11:25 AM:
> Hi,
>
> In preparation to implementing the clover plugin for m2, I
> need to understand what are the options WRT generated
> sources. Indeed clover modifies the source files (.java
> files) and generate instrumented source
Hi Vincent,
I'm not sure that I understand all of the problems you mention but I
think it is important to propagate instrumented source code over
multiple projects, e.g. I tweaked the clover plugin and various build to
create instrumented artifacts over multiple project, where the final WAR
was
Hi,
In preparation to implementing the clover plugin for m2, I need to
understand what are the options WRT generated sources. Indeed clover
modifies the source files (.java files) and generate instrumented source
files.
I can see 2 options:
1/ Option 1: A mechanism similar to the Ant task where
24 matches
Mail list logo
