I am fine with any solution! Uwe
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Chris Hostetter [mailto:[email protected]] > Sent: Monday, September 22, 2014 6:16 PM > To: [email protected] > Subject: RE: Help with `ant beast` > > > : I would prefer to change the parent modules to have an explicit target. See > my other message. > > you're missing the point -- you can do both. > > Add an explicit top level beast target w/whatever message you think is best. > but in general, if you've got a target that has preconditions, and you don't > like > the message that target fails with when the preconditions aren't met, then > add an explicit check of those preconditions and fail with a better message. > > yes junit.classpath is an implementation detail, but it's a detail of the same > target where you can add this <fail> ... whatever the implementation details > are, you can add the same check. > > that way you are protecting hte target (and it's error messages) from any > possible overside in forgetting to add an explicit "override" with a helpful > error, or if the build.xml files are refactored, or if the directories are > moved > arround, etc... > > : > : ----- > : Uwe Schindler > : H.-H.-Meier-Allee 63, D-28213 Bremen > : http://www.thetaphi.de > : eMail: [email protected] > : > : > : > -----Original Message----- > : > From: Chris Hostetter [mailto:[email protected]] > : > Sent: Friday, September 19, 2014 6:56 PM > : > To: [email protected] > : > Subject: RE: Help with `ant beast` > : > > : > : > : > : 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. > : > > : > can we just add something like this inside the "beast" target?... > : > > : > > : > <fail message="The Beast wonly orks inside of individual modules (where > : > 'junit.classpath' is defined)"> > : > <condition> > : > <not><isrefrence refid="junit.classpath"/></not> > : > </condition> > : > </fail> > : > > : > > : > > : > : > : > : 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] > : > : > : > : > : > > : > -Hoss > : > http://www.lucidworks.com/ > : > : > : --------------------------------------------------------------------- > : To unsubscribe, e-mail: [email protected] > : For additional commands, e-mail: [email protected] > : > : > > -Hoss > http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
