From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

In a way. Gradle is using reflection to read and serialize the fields of `SerializedLambda`when it could be using the exposed API.

I'm not sure how I can workaround this. I have added `serializableFunctionOf`, `serializableTransformerOf` etc around lambdas in my plugin :confused:

I guess the issue is that one serialized lambda uses `collect(...)` and that collector cannot be serialized.

Ok I have found a workaround for this one by not passing the collector as an argument, on to the next error...

does that ring a bell?
```Caused by: java.lang.ClassCastException: class org.gradle.api.internal.file.DefaultFileCollectionFactory$ResolvingFileCollection cannot be cast to class org.gradle.api.artifacts.Configuration (org.gradle.api.internal.file.DefaultFileCollectionFactory$ResolvingFileCollection and org.gradle.api.artifacts.Configuration are in unnamed module of loader org.gradle.internal.classloader.VisitableURLClassLoader @4cdf35a9)
        at org.graalvm.buildtools.gradle.NativeImagePlugin.$renamedDeserializeLambda$(NativeImagePlugin.java:153)
        at org.graalvm.buildtools.gradle.NativeImagePlugin.$deserializeLambda$(NativeImagePlugin.java)
        ... 170 more```

(sorry no scan because.... happens at configuration time!)

this seems to be caused by this call:
&gt; Set&lt;ResolvedComponentResult&gt; components = classpath.getIncoming().getResolutionResult().getAllComponents()

It looks related to how the configuration cache serialization turns `Configuration` objects into simpler `FileCollection`s

Any implicitly captured variable holding a `Configuration` instance must be explicitly typed as `FileCollection`