This message was deleted.
# configuration-cache
s
This message was deleted.
v
Hopefully not. (necessary to do so) The classpath gets instrumented by Gradle which uses bytecode manipulation to insert
Instrumented...
calls to all code, even libraries or whatever that you use to automatically gather the relevant CC inputs. I'd expect it to also work automatically in init scripts. But just try it and see whether changing the file will invalidate the CC entry.
Besides that this code looks like many internals being used, so you should maybe not replicate it but use the official way?
Besides that it might be a bad idea to define a version catalog from an init script unless that init script is part of a custom distribution.
c
Thanks for the info, hopefully the CC works out smoothly. The init script doesn't do everything in there and only uses the public API to do what's needed. I was mostly concerned about the CC specifics.
v
Yeah, that should hopefully just work.
c
unless that init script is part of a custom distribution
It is exactly that. We don't use stock Gradle.
👌 1