Hi Steve, This is correct! Maybe we can improve the error message, but this is not so easy... What is the best way to detect if a build file is a parent one? Of course we could add a dummy target to all parent build files - "ant test" has this to delegate to subant builds, but we don’t want to do this here.
Uwe ----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Steve Rowe [mailto:[email protected]] > Sent: Friday, September 19, 2014 5:54 PM > To: [email protected] > Subject: Re: Help with `ant beast` > > I think ‘ant beast’ only works in the directory of the module containing the > test, not at a higher level. > > On Sep 19, 2014, at 11:45 AM, Ramkumar R. Aiyengar > <[email protected]> wrote: > > > I am trying to use `ant beast` on trunk (per the recommendation in test- > help) and getting this error: > > > > ~/lucene-solr/lucene> ant beast -Dbeast.iters=10 -Dtests.dups=6 > > -Dtestcase=TestBytesStore > > > > -beast: > > [beaster] Beast round: 1 > > > > BUILD FAILED > > ~/lucene-solr/lucene/common-build.xml:1363: The following error > occurred while executing this line: > > ~/lucene-solr/lucene/common-build.xml:1358: The following error > occurred while executing this line: > > ~/lucene-solr/lucene/common-build.xml:961: Reference junit.classpath > not found. > > > > `ant test` works just fine. Any idea where the problem might be? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
