Build cache is documented as building upon up-to-date checks, and up-to-date checks documentation says that

@Nested

property types do not have to be

Serializable

as long as they have annotated input properties of serializable types, and there's even an example of that. I also see that the Jacoco plugin does not have its

JacocoAgent

CommandLineArgumentProvider

and

JacocoPluginExtension

(used by that object as a

@Nested

property) marked as

Serializable

. So why would my plugin which follows the same pattern trigger build cache misses due to build cache key differences for those

@Nested

properties (but not the other input properties they carry)? https://github.com/tbroyer/gradle-errorprone-plugin/issues/101, with an apparent fix being to make those types `Serializable`: https://github.com/tbroyer/gradle-errorprone-plugin/pull/102 I have nothing against making this change but do you think this is a bug in Gradle?