That sounds good. Btw, I first tried it at the toplevel, and that came back with a beast target not found, hence went to lucene subdir. At least that's guessable, so less important, would be to add that failure message to the toplevel as well.. On 19 Sep 2014 18:02, "Ryan Ernst" <[email protected]> wrote:
> > On Fri, Sep 19, 2014 at 9:55 AM, Chris Hostetter <[email protected] > > wrote: > >> 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> >> > > +1 >
