> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: samedi 8 avril 2006 16:15
> To: Maven Developers List
> Subject: Re: Feedback needed on clover aggregation feature I'd like to
> implement...
>
> It doesn't sound right, classif
lly thought it out so I may discover other issues
> along the way.
>
> Let me know if you think I'm going in the right direction...
>
> Thanks
> -Vincent
>
>> -----Original Message-----
>> From: John Casey [mailto:[EMAIL PROTECTED]
>> Sent: mer
mercredi 5 avril 2006 20:47
> To: Maven Developers List
> Subject: Re: Feedback needed on clover aggregation feature I'd like to
> implement...
>
> You'd need an ArtifactFactory and an ArtifactResolver, along with the
> repository list and the local repository...I think
You'd need an ArtifactFactory and an ArtifactResolver, along with the
repository list and the local repository...I think that's it.
Once you have these, you can use the original artifact to create a new
one with the "clover" classifier, then feed that into the
ArtifactResolver, along with the
Here's an update so far (see below).
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: mercredi 5 avril 2006 12:58
> To: 'Maven Developers List'
> Subject: Feedback needed on clover aggregation feature I'd like to
> implement...
>
> Hi,
>
> I've just realized
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: mercredi 5 avril 2006 17:51
> To: 'Maven Developers List'
> Subject: RE: Feedback needed on clover aggregation feature I'd like to
> implement...
>
> While trying to im
While trying to implement what's below, I've found a snag.
Here's a typical pom using clover for checking code coverage:
org.apache.maven.plugins
maven-clover-plugin
1%
main
verify
> -Original Message-
> From: Mike Perham [mailto:[EMAIL PROTECTED]
> Sent: mercredi 5 avril 2006 15:52
> To: Maven Developers List
> Subject: RE: Feedback needed on clover aggregation feature I'd like to
> implement...
>
> Wow, that sounds cool. We
Wow, that sounds cool. We're already blown away by the aggregated report.
On second thought, I think that feature, while nifty, is not high priority. In
fact I believe we would disable it if possible. A module's unit tests should
exercise its code as much as possible and not rely on other mod
