Hi Peter, I have since discovered it is not a bug in Gradle... Some fool put a System.exit(1) in our server startup code instead of throwing a Runtime. That cost me way too much time. Many thanks for including the exit value in the output and Sorry for any noise caused by reporting the original issue. Keep up the good work guys.
Cheers, Adrian. On Jan 28, 2011, at 11:23 PM, Peter Niederwieser <[email protected]> wrote: > > The exit value is now included in the log message. Please submit a JIRA issue > with all information you have (ideally a runnable build demonstrating the > problem). > > -- > Peter Niederwieser > Developer, Gradle > http://www.gradle.org > Trainer & Consultant, Gradle Inc. > http://www.gradle.biz > Founder, Spock Framework > http://spockframework.org > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Gradle-Worker-1-finished-with-non-zero-exit-value-tp3359304p3361612.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 > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
