-
Bug
-
Resolution: External
-
P4
-
None
-
9, 10
Setting a new environment variable or updating an existing env variable will not be picked up by the FX build if the gradle daemon is running.
To reproduce this, run the following command without ANT_HOME set and without ant in your PATH:
gradle apps
It will fail trying to build the apps because ant is not found. Now try to fix it:
export ANT_HOME=/path/to/ant
export PATH=${PATH}:$ANT_HOME/bin
gradle apps
It will not pick up the new env setting and the build will still fail.
gradle launches a daemon by default. It will reuse this daemon for subsequent builds in the same directory as long as the build.gradle file and the JDK version uses to run the build is the same.
When building using JDK 9 (which is the minimum required version for jfx-dev), the environment variable settings that were in effect at the time the gradle daemon was launched are used for all subsequent builds that run using that daemon.
Workround: stop the gradle daemon with 'gradle --stop' whenever you change env settings (or don't use the gradle daemon in the first place).
To reproduce this, run the following command without ANT_HOME set and without ant in your PATH:
gradle apps
It will fail trying to build the apps because ant is not found. Now try to fix it:
export ANT_HOME=/path/to/ant
export PATH=${PATH}:$ANT_HOME/bin
gradle apps
It will not pick up the new env setting and the build will still fail.
gradle launches a daemon by default. It will reuse this daemon for subsequent builds in the same directory as long as the build.gradle file and the JDK version uses to run the build is the same.
When building using JDK 9 (which is the minimum required version for jfx-dev), the environment variable settings that were in effect at the time the gradle daemon was launched are used for all subsequent builds that run using that daemon.
Workround: stop the gradle daemon with 'gradle --stop' whenever you change env settings (or don't use the gradle daemon in the first place).
- relates to
-
JDK-8191621 Windows build fails if VS150COMNTOOLS is set
-
- Resolved
-
- links to