Hi Erwan,

Ignore this paragraph since I wrote it will you were making the changes that 
solved the problem:
I agree with Jacopo, I really think the best solution would be to just have 
users that want cobertura run the separate ant task that downloads it instead 
of doing it automatically for them.  We are allowed optional dependencies of 
non-compatible libraries but I think the automatic download when running tests 
crosses the line in a mandatory dependency.

Also another thing to keep in mind for any feature is that a change that makes 
life easier for you won't necessarily make life easier for everyone.  For 
example, I never look at the cobertura reports when running tests but now I 
have to wait while the library is downloaded (not sure what happens when I'm 
offline) and also put up with longer run times because of the additional 
overhead of the instrumentation.

I'm not complaining though, just wanted to take the opportunity to again 
highlight that sometimes certain additional features can be as much of a 
hindrance to some as they can be a help to others.

Regards
Scott

On 8/06/2011, at 10:08 PM, Jacopo Cappellato wrote:

> Hi Erwan,
> 
> I doubt it will be enough to resolve this concern about the ASF licensing 
> policy.
> 
> Jacopo
> 
> On Jun 8, 2011, at 11:49 AM, Erwan de FERRIERES wrote:
> 
>> Le 08/06/2011 10:07, Scott Gray a écrit :
>>> I'm still not comfortable with the run-tests build target automatically 
>>> downloading a GPL dependency, I don't think that should've been added 
>>> without some sort of indication that it's inline with ASF licensing 
>>> policies.
>>> 
>> Hi Scott,
>> 
>> there is the clean-downloads task which removes all the downloaded files. 
>> Should it be added to the build script ?
>> 
>> -- 
>> Erwan de FERRIERES
>> www.nereide.biz
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to