JDK-8088325 : FX needs to be aware of JDK module system constraints or layout in locating JDK fonts
- Type: Bug
- Component: javafx
- Sub-Component: graphics
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-07-11
- Updated: 2018-01-19
- Resolved: 2016-11-09
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 :
|
|
|
Relates :
|
|
|
Relates :
|
Description
JDK project jigsaw is proposing changes to the layout of the JDK that would initially (at least) move the JDK fonts from lib/fonts to conf/fonts. Since FX digs into the JDK to get fonts it needs to be updated to be aware of this potential change and so to be ready for it. That is the minimum work needed here. Further down the road as jigsaw may consider the on-disk image layout to be completely private and perhaps not even accessible in a fixed stable manner, then a modular JavaFX might need to explicitly depend on a JDK fonts module and use an API from that to determine the location of the fonts. Either that or FX duplicates the fonts it needs :-(
Comments
|