Lóránt Pintér

For the migration we can stay as close to the current APIs, and for example replace `List` with `ListProperty`. Later we can revisit this API and introduce something like `DomainObjectCollection`...

There is also the concept of "conditional nested", i.e. when we'd create some sort of container for `CompileOptions.debugOptions` that's only available to configure (and capture as an input) if `CompileOptions.debug`...

What is missing for this so that we can close it?

As @ov7a mentioned, this is not inline with how Gradle thinks about the structure of the build. Tasks are defined in the context of their inputs and outputs, from which...

I think this should have been fixed in Gradle 7.5 by: https://github.com/gradle/gradle/pull/20200 Can you reproduce with a recent version?

Hey @dturner, sorry, just noticed your comment. > > Use existing plugins and run against upgrade provider API-compatible properties in Gradle. > > I have a few questions if you...

Another option could be to remove stricter validation as a separate option, and make it the only option. The only difference this would make is that inputs on tasks not...

Thanks for the offer of PRs, but the difficulty is not so much in flipping this switch itself, but in how we handle the change. Flipping the switch directly would...

Adding support for lint-like tasks that modify their own inputs has been on our radar for some time, but there is no plan to implement this feature in the foreseeable...

I agree that there is a dependency on the value of `PATH` which is unfortunate. However, even if we resolved the executable, it would not account for all inputs properly....