Dinesh Patil wrote:
> I didn't see the obvious failure from the huge complete build.errs or
> short build.errs.filtered as well.. This seems to be the output of build
> and javadoc command, so error may be later on..
There's a whole bunch of code that doesn't compile successfully.
Why is that not an obvious build failure?
> Attaching the file which shows the compiler failure, so I believe if you
> specify the failure patterns instead of success patterns, finding errors
> may be quicker and shorter logs. You can see from my attached
> compilefail.txt file, failure patterns are
> BUILD FAILED
> Compile failed
> [ERROR] Java Result: 1
That doesn't tell you *what* failed, that only tells you *that* it
failed. Determining that it failed isn't the issue.