From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

working on making my plugin not break with the configuration cache. Does this collection of annotations even make sense? Gradle doesn't complain in any obvious way
```@Transient
@get:PathSensitive(PathSensitivity.RELATIVE)
@get:InputFiles
lateinit var projectHealthReports: Configuration```
Specifically, I've added `@Transient` so that Gradle doesn't serialize the `Configuration` instance. For input hashing, I want it to treat the property as a collection of files, but in the task action I use APIs only available on `Configuration`

a-ha. Running the build twice leads to a failure, because the property isn't initialized. That makes sense!

Why just not use `ConfigurableFileCollection#from(Configuration)`?

as I said, I specifically want the APIs available on `Configuration` for this use-case. `FileCollection` isn't sufficient.

Ah, missed the last bit. Thought about file collection + configuration name to get the same configuration back but it will still fail with cc(

I'm hoping I can find a better solution in the medium-term future. With Gradle 7.5, it seems like it might be possible for my plugin to actually be compliant. (I need the lazy graph analysis)