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