Are you using any of the @InputX @OutputX annotations for the task properties?
- Hans -- Hans Dockter Founder, Gradle http://www.gradle.org, http://twitter.com/gradleorg CEO, Gradle Inc. - Gradle Training, Support, Consulting http://www.gradle.biz On Tue, Jul 6, 2010 at 2:58 PM, Chris Beams <[email protected]> wrote: > tried; got the same result. > > On Jul 6, 2010, at 2:53 PM, Hans Dockter wrote: > > Hi Chris, > > could you try running this with the option (cleaning the cache): -C rebuild > > - Hans > > -- > Hans Dockter > Founder, Gradle > http://www.gradle.org, http://twitter.com/gradleorg > CEO, Gradle Inc. - Gradle Training, Support, Consulting > http://www.gradle.biz > > > On Tue, Jul 6, 2010 at 2:34 PM, Chris Beams <[email protected]> wrote: > >> I'm seeing the following: >> >> > org.gradle.api.UncheckedIOException: Could not add entry ':uploadDoc' to >> cache >> '/Users/cbeams/Work/myproject/.gradle/0.9-preview-3/taskArtifacts/cache.bin'. >> >> >> further down the stack trace, the root cause reads: >> >> > Caused by: java.io.NotSerializableException: Login_Decorated >> >> >> Where 'Login' is the name of a task I've defined in buildSrc that extends >> DefaultTask >> >> If I update the definition of the Login task such that it 'implements >> java.io.Serializable', I then get the same stack trace, but instead of >> complaining about 'Login_Decorated', it is now a gradle-internal class >> causing issues >> >> > Caused by: java.io.NotSerializableException: >> org.gradle.api.internal.ConventionAwareHelper >> >> The task in question (:uploadDoc) actually completes successfully, but the >> build overall fails due to the exception being thrown when trying to write >> to the cache. >> >> Ring any bells? I don't see anything about task serializability in the >> docs, etc. >> >> Thanks, >> >> - Chris Beams >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > >
