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 Massol wrote: > 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 a block of >> source into every source file for instrumentation purposes. cpd sees >> this block of code as copy/pasted code because it occurs in every source >> file and fails my build. >> >> Who's in the wrong here? I'm inclined to say it's a Clover plugin bug >> because it should not be exposing its modified code as source to be >> examined by other plugins. > > The clover plugin makes all its changes in a forked lifecycle in order not > to impact the main build lifecycle. However the issue I have is how to > "exclude" some goals from executing while in the forked lifecycle. > > This is a big issue and I don't have the answer right now... > > I'd appreciate any help here. > > Thanks > -Vincent > > > > > > > ___________________________________________________________________________ > Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs > exceptionnels pour appeler la France et l'international. > Téléchargez sur http://fr.messenger.yahoo.com > > --------------------------------------------------------------------- > 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]
