Sterling Greene

Changing `WindowsResourceCompile` to use a `ListProperty` for compiler args is the way to go. I think we can still punt on the macro/`MapProperty` question and leave it as-is.

What we would like to do is to set a pattern that maps components with multiple variants and capabilities into particular coordinates automatically. Gradle would take care of the mapping...

We'll take a look at this PR for 8.9.

related https://github.com/gradle/gradle/issues/28110

This is a real problem that needs to be addressed holistically. Some ideas: - Treat `PATH` as a compatibility criteria for Gradle daemons. This would mean we would start more...

@mhsmith I don't see that with newer versions of Gradle. I can reproduce it with 6.5. Putting this in build.gradle: ``` println "ENV_VAR=" + System.env.ENV_VAR ``` And running with Java...

@tagae Are you referring to problems with PATH or any environment variable? Using macOS, Java 21.0.1, 8.8-rc-1, I have this in a build.gradle: ``` println "ENV_VAR=" + System.env.ENV_VAR project.exec {...

> I was considering only the `PATH` env var (sorry for the noise). Ah, thanks! I thought that might be what you meant. > Of the https://github.com/gradle/gradle/issues/10483#issuecomment-2135736533, this seems the...

This needs to be refreshed for 8.8. We'll take a look at it then.

Sorry, it's encouraging to see that you were using this API. Incubating APIs are subject to change and we're not going to roll back to the old names in 8.7/8.8....