Isn't the problem that the clovered part is meant to be a separate,
forked, lifecycle - but the PMD goals (etc) are still bound when they
are only wanted on the main lifecycle?
- Brett
On 11/07/2006 6:33 AM, Mike Perham wrote:
I think Maven 2.1 needs to differentiate between the original project
sources and "currently effective" generated sources. Report plugins act
on the former, build plugins on the latter. I don't know that it is
possible to solve this problem in 2.0.x.
-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 3:17 PM
To: 'Maven Developers List'
Subject: RE: General issue with clover plugin requiring creative
thinking...
Well that's the other way of doing it. But then how do you tell other
plugins (like compile, jar, install, deploy, cargo, etc) that they
should
act on clovered sources and not on standard sources?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
