JDK-8169747 : javac @compile.args does not pick up changes in local build
- Type: Bug
- Component: javafx
- Sub-Component: build
- Affected Version: 9
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- Submitted: 2016-11-16
- Updated: 2016-11-18
- Resolved: 2016-11-18
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9Fixed  |
Related Reports
|
Relates :
|
Description
The newly generated rt/build/compile.args file uses --upgrade-module-path to point to the recently built local javafx.* modules. This does not correctly pick up any modified or added classes, presumably because the javafx.* modules in the JDK are not upgradeable. Instead we probably need to use --patch-module as is done in the run.args file. If I take run.args and strip out the -Djava.library.path (which I thought was the intention for compile.args) then it works correctly for a simple test case. The testcompile.args will likely need the same change.
Comments
|