buildr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lacton <lac...@users.sourceforge.net>
Subject Re: Emma and Cobertura getting to good for addon Re: svn commit: r700747 - /incubator/buildr/trunk/rakelib/rspec.rake
Date Mon, 06 Oct 2008 12:28:22 GMT
Assaf,

On Mon, Oct 6, 2008 at 2:07 AM, Assaf Arkin <arkin@intalio.com> wrote:
> On Sun, Oct 5, 2008 at 12:32 PM, lacton <lacton@users.sourceforge.net> wrote:
>> Moving Emma and Cobertura to lib is fine with me.
>>
>> One thing I'd like to keep is that the extension should be loaded only
>> if required by the user or the buildfile.  Right now, the way the
>> Emma/Cobertura extensions work is to add the test coverage tool to the
>> test task's dependencies and to add the instrumentation step before
>> testing.  I don't want to penalize users that don't want to measure
>> their test coverage.
>>
>> My understanding is that, currently, everything in lib is required
>> during startup.  Should we add an 'optional import' directory in lib?
>
> You have to require 'buildr/groovy' explicitly, but you're compensated
> for your effort by having the Groovy compiler handle both Java and
> Groovy source files.  So it's not without precedent to have stuff in
> lib that's loaded explicitly.

Thank you for reminding me of this fact.

In that case, I'd like to move the two test coverage tools to lib/ as
soon as the 1.3.3 release is done.

If later we find that lib/ is too bloated for our taste, we can always
use the separate gem tactic at that time.

Lacton

Mime
View raw message