Using a snapshot gradle install would be problematic for us as we have many users (and it looks hackish).
Could you give some guidance as to the m5 release? If it's 2 days out we would probably opt to wait. If it's 2 weeks out, we might just use a snapshot. Thanks phil On Tue, Sep 6, 2011 at 7:21 PM, Adam Murdoch <[email protected]> wrote: > > On 07/09/2011, at 8:06 AM, phil swenson wrote: > > We are having a lot of troubles with error like this on our Jenkins > job: http://issues.gradle.org/browse/GRADLE-1472 > We also get many cache corruption errors. > > Could someone make a suggestion on either preventing these problems > and/or setting up a "clean" job on Jenkins so we can clean up all the > problems when they occur? > > These cache corruption issues are fixed in master, and these fixes will be > included in the 1.0-milestone-5 release. So, one workaround is to upgrade to > a recent nightly snapshot. > > -- > Adam Murdoch > Gradle Co-founder > http://www.gradle.org > VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting > http://www.gradleware.com > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
