Nikolay Metchev

> @NikolayMetchev Wow Can you give more information about the gradle hack? The idea is to delete the `/META-INF/services/org.mapstruct.ap.spi.AccessorNamingStrategy` file from `protobuf-spi-impl.jar` build.gradle.kts ``` val artifactType = Attribute.of("artifactType", String::class.java) val...

These plugins are no longer being maintained by the looks of things. That is why we have stopped using them and replaced them with shell scripts.

sorry I have deleted my fork.

That's not me

I think if that is changed to relative the comment will still stand with the added benefit of allowing cache reuse across CI runs.

I created a PR. Let me know if it works? https://github.com/autonomousapps/dependency-analysis-gradle-plugin/pull/1107

I am a little confused. I feel like the only thing that should be writing to the gradle home directory are core tasks and not any of the tasks that...

The change in my PR only affects inputs and not outputs anyway.

The output report doesn't refer to jars. it only references dependencies. Here is a sample: ``` Advice for :test:aws:cedar Unused dependencies which should be removed: api(libs.aws.lambda.java.core) api(libs.aws.lambda.java.events) api(libs.aws.sdk.kotlin.lambda) implementation(libs.jsonassert) implementation(libs.kotlinx.serialization.core)...

It seems there are some intermediate outputs in json that contain absolute paths. I guess we need to change those to be relative paths and then we should be good...