search

gradlex-org / jvm-dependency-conflict-resolution

Gradle plugin to improve Dependency Conflict Detection and Resolution
http://gradlex.org/jvm-dependency-conflict-resolution/
Apache License 2.0
52 stars 14 forks source link

Configuration cache state could not be cached #157

Closed sschuberth closed 2 months ago

sschuberth commented 3 months ago

With version 2.1.2 of the org.gradlex.jvm-dependency-conflict-detection plugin running on Gradle 8.10 and Kotlin 2.0.20 I'm getting:

* What went wrong:
Configuration cache state could not be cached: field `provider` of `org.gradle.internal.serialize.codecs.core.ProviderBackedFileCollectionSpec` bean found in field `element` of `java.util.Collections$SingletonList` bean found in field `elements` of `org.gradle.internal.serialize.codecs.core.ResolutionBackedFileCollectionSpec` bean found in field `__classpathSnapshot__` of `org.jetbrains.kotlin.gradle.tasks.KotlinCompile$ClasspathSnapshotProperties` bean found in field `__classpathSnapshotProperties__` of task `:notifier:compileKotlin` of type `org.jetbrains.kotlin.gradle.tasks.KotlinCompile`: error writing value of type 'org.gradle.api.internal.provider.DefaultProvider'
jjohannes commented 2 months ago

The error looks like something that is happening in the Kotlin plugin. Can you please provide a reproducer?

This – https://github.com/jjohannes/gradle-project-setup-howto/tree/kotlin – is a project with:

I do not get any errors in that project.

sschuberth commented 2 months ago

When I created this, I was able to reproduce the issue with https://github.com/oss-review-toolkit/ort/tree/jvm-dependency-conflict-resolution and running ./gradlew assemble (I believe). However, when I just tried again, I cannot reproduce this anymore. But maybe that's just because of some cached result being reused on my end?

jjohannes commented 2 months ago

Alright. I am closing this issue. Feel free to comment again or open a new issue if you have a reproducer that indicates that there is a problem in this plugin.