Cédric Champeau
Cédric Champeau
The very same error seems to happen when using Java Toolchains support and GitHub actions windows runners (`runs-on: windows-2016`).
Any workaround for this problem? It currently blocks testing Windows builds on GitHub actions... I should mention that in my case it seems to happen with TestKit: the Gradle build...
There was an issue in `gradle/gradle` which was closed in favor of this one: https://github.com/gradle/gradle/issues/16656 Since yesterday I have setup a Windows 10 VM and I can confirm the same...
I think this error can happen if you have dependencies in an init script. Could you check?
Hi @forax , Do you know of any workaround in JDK 9? Basically the JDK makes immutable something which is inherently mutable (the environment variables), and Gradle needs to set...
As far as I understand `ProcessBuilder` doesn't solve the problem: it doesn't allow mutating the environment of an _existing_ process, which is what the daemon needs to do.
Yeah it is unclear if the modifications are _immediately_ visible to processes (already started), or only to processes started after the modification. But it's an interesting thing to check, it...
Dalibor Topic just told me it modifies the subsequent processes, not the current one, so it's not a suitable option...
Follow up discussion is on [core-libs-dev](http://mail.openjdk.java.net/pipermail/core-libs-dev/2017-May/047588.html)
That's a good idea, I faced the very same problem today. Basically I had to put both the `highlightjsdir` attribute in my Gradle configuration so that it fetches a local...