> -Original Message-
> From: Mike Perham [mailto:[EMAIL PROTECTED]
> Sent: mardi 30 mai 2006 17:56
> To: Vincent Massol
> Subject: RE: clover and cpd plugin clashes
>
> I would argue that the modified Clover code should not be reported on at
> all.
Agreed
Hi Mike,
(answering an email from the past that I hadn't processed and was still
sitting in my inbox)
> -Original Message-
> From: Mike Perham [mailto:[EMAIL PROTECTED]
> Sent: mercredi 12 avril 2006 00:35
> To: Maven Developers List
> Subject: clover and cpd plugin clashes
>
> So this i
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 12 avril 2006 05:31
> To: Maven Developers List
> Subject: Re: clover and cpd plugin clashes
>
> Yep, that's definitely a limitation. Something to think about.
>
>
Yep, that's definitely a limitation. Something to think about.
I didn't think CPD would check generated sources, though - perhaps
that's something to change?
The only workaround I can think of is to bind the cpd check to something
later than clover executes, such as "verify".
- Brett
Vincent M
Hi Mike and all,
> -Original Message-
> From: Mike Perham [mailto:[EMAIL PROTECTED]
> Sent: mercredi 12 avril 2006 00:35
> To: Maven Developers List
> Subject: clover and cpd plugin clashes
>
> So this is an interesting bug.
>
> I have clover and pmd:cpd-check configured. Clover injects
