Yep, fixed that. The deadlock on the wrong jdk must be new in the updated Hudson.
-----Original Message----- From: Benjamin Bentmann [mailto:[EMAIL PROTECTED] Sent: Thursday, July 31, 2008 4:15 AM To: Maven Developers List Subject: Re: CI job maven-shared: fail-at-end? Brian E. Fox wrote: > Fixed now, never seen that happen before so I'll keep an eye out. Thanks! Can you also have a look at https://ci.sonatype.org/job/maven-2.0.10-RC/2/console I assume the job needs to be reconfigured to use Java 1.5 or each build will deadlock again. Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
