Open Naitbit opened 1 year ago
Still happens with artifactregistry-gradle-plugin:2.2.1 Gradle 8.1.1 Linked docs
I've created Proof of Concept that updates Gradle plugin to Gradle 8.1.1 and fixes the configuration cache issue. https://github.com/Naitbit/artifact-registry-maven-tools/commit/35f6c550428c2752f4a6c085bb43aa9872af7e37 To be complete it would also require making compatibility adjustments in Maven Wagon, which I don't use and didn't test.
Any news on this? Or workarounds?
Well I did build my branch locally and put .jar as dependency. It fixed CC complain, but I'm not vouching for my accidental fork.
As workaround, you can apply the plugin conditionally only for publishing builds. It's not very nice but works. This means:
--no-configuration-cache
(otherwise build fails with unsupported repository type as the plugin is not active).if (!serviceOf<BuildFeatures>().configurationCache.active.get()) {
apply(plugin = "com.google.cloud.artifactregistry.gradle-plugin")
}
Won't work for us. We are using the plugin mainly to handle the access to the artifact maven repo. I am considering to create a PR for this repo with a fix, that is based on Naitbits fork
I've created a new Gradle Plugin: https://github.com/bjoernmayer/artifactregistry-gradle
When trying to use artifactregistry-gradle-plugin:2.2.0 with Configuartion Cache Gradle 8.1 it errors out with:
1 problem was found storing the configuration cache.