On 27/03/2012, at 12:38 AM, Philip Crotwell wrote: > Hi > > I have a patch for GRADLE-2084 where serialization exceptions cause > gradle to crash rather than simply failing the out of date check.
I don't think this is the correct solution for this issue. That code is used for a number of different things, not just for task up-to-date checks. There are many ways an IncompatibleClassChange can happen here, and for almost all of them, we don't want to ignore the exception. Instead, I think we want to do this: http://issues.gradle.org/browse/GRADLE-1910. This will catch the incompatible changes to persistent classes, plus a whole bunch of other problems. A fix is scheduled for 1.0-rc-1. -- Adam Murdoch Gradle Co-founder http://www.gradle.org VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting http://www.gradleware.com
