river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Hobbs" <tvho...@googlemail.com>
Subject Re: ServiceDiscoveryManager test coverage
Date Sun, 22 Aug 2010 20:02:24 GMT
Quickest (and dirtiest) method I can think is to just comment out the guts  
of the javadoc target in your build.xml.

That way you won't have lots of other targets complaining about missing  
dependencies.

Ideally, setting the build.xml to build (or not build) if some flag is set  
would be a good idea.



On Sun, 22 Aug 2010 17:15:11 +0100, Patricia Shanahan <pats@acm.org> wrote:

> On 8/21/2010 10:17 PM, Patricia Shanahan wrote:
> ...
>> Tomorrow, unless I get a better idea or someone posts one, I'll start a
>> binary search. The objective will be to find consecutive revisions N and
>> N+1 such that N passes the servicediscovery tests and N+1 fails them.
>
> I don't have a better idea, so I'm doing the binary search. Is there an  
> easy way of making it build everything except the javadocs? I don't need  
> them for my testing, and they seem to take a significant amount of time  
> during the build.
>
> Patricia


-- 
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Mime
View raw message