On Mon, Oct 14, 2013 at 12:46 PM, Dawid Weiss <dawid.we...@cs.put.poznan.pl> wrote:
> This isn't an error condition (to me). Wait, I think it is an error :) Yes, a hard to fix error (our test infra is complex), but still an error. Ie, if I ask "ant test" to run a specific test, and it finds no such test, yet declares "BUILD SUCCESSFUL" in the end, how can such lenient error checking be good? It's trappy. It's like "javac foo.java" returning successfully when foo.java doesn't exist. I'm not using wildcards when I ask it to run a test :) Sure, maybe wildcards are used under the hood, but this is an implementation detail. Maybe a simple compromise: could we make a new ant target, "run-specific-test-for-certain", whose purpose was to run that test and fail if no such test was not found? I think it's fine if this only works at the "module" level, if ant makes it too hairy to recurse. Mike McCandless http://blog.mikemccandless.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
