Mailing-List: contact river-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4CE78B08.9000005@qcg.nl>
Date: Sat, 20 Nov 2010 09:47:04 +0100
From: Sim IJskes - QCG <sim@qcg.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10
MIME-Version: 1.0
To: river-dev@incubator.apache.org
Subject: Re: ant run-tests does too much
References: <4CE6F165.1070104@acm.org>
In-Reply-To: <4CE6F165.1070104@acm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 11/19/2010 10:51 PM, Patricia Shanahan wrote:
> I'm having a problem with "ant run-tests" doing too much, and taking too
> long to get to the test in question.
>
> Even when run immediately after an all.build, so that all jars are up to
> date, it goes through a lot of deleting and build jars.
>
> Can anything be done about this? Is there some alternative target I can
> use that does not force rebuilding? Quick running of a single test is
> very important for debug.

I'm assuming you work with the latest version. Do you want to keep 
running a single test in a loop? Thats the only reason i can think of 
where you wouldn't like to build the harness-runtime and underlying 
river-runtime.

If you are in a hurry, just remove the harness dependency in the 
run-tests target.

Shall i include a target run-tests-nodep?

Gr. Sim