Jérôme Prinet
Jérôme Prinet
The `@Classpath` annotation or the `@PathSensitive(PathSensitivity.RELATIVE)` would only have some influence on the way the task cache key is computed. The underlying file collection would still contain all the data...
> I don't understand the problem with NONE. It was my understanding that this instructs Gradle that the path to the file doesn't matter, and that the only thing we...
> 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...
According to @autonomousapps, there are [some cases](https://github.com/autonomousapps/dependency-analysis-gradle-plugin/issues/1083#issuecomment-1904596620) where the outputs contain paths to Gradle user home.
I was wondering if "just" using a relative path could help. That would be a simpler change but I'm unsure of the implications / feasibility
[This commit](https://github.com/micronaut-projects/micronaut-build/commit/dc2e2def2107d91914160eb3c37c4172953250ed) fixed it, thanks @ribafish!
Sorry for the late reply @nedtwigg I could eventually identify the root cause after investigating further the issue. The cache key differs when running the build from different locations due...
I can confirm that the `steps` input property is fingerprinted with the Java serialization result. You can see in this screenshot the absolute path to the settings file (in addition...
> Do you think it could work with a relative path being passed? any chance you could consider this option @nedtwigg ? If not, will you implement a fix?