Try a newer version (build yourself or a nightly build), I've noticed some big changes over the past little while in regard to default output (I think I like it :) ), test failures, and performance (yep, it's faster now).
On Sat, May 29, 2010 at 18:25, Peter Niederwieser <[email protected]> wrote: > > Today I tried Gradle 0.9-preview-1 and noticed that messages of failed Spock > tests no longer appear anywhere - not on the console, not in HTML reports, > not in XML test results (with Gradle 0.8 this works fine). I think the > problem is that, for some reason, the AssertionError's (subclasses) thrown > by Spock get translated to AssertionFailedError's (a JUnit 3 class), but the > exception message isn't successfully copied over because Spock's exception > classes return null for getMessage(). This can be considered a Spock bug and > will be fixed (probably I've never hit this problem before because all the > tools calls toString() and print that). But why does Gradle now translate > all exceptions (at least all AssertionError's) to AssertionFailedError's? Is > this an intentional change? > > Cheers, > Peter > -- > View this message in context: > http://old.nabble.com/Gradle-now-translates-all-test-failures-to-AssertionFailedError%27s---why--tp28719387p28719387.html > Sent from the gradle-user mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > -- Jason Porter Software Engineer Open Source Advocate PGP key id: 926CCFF5 PGP key available at: keyserver.net, pgp.mit.edu --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
