-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b38
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8082001 | emb-9 | Roger Riggs | P3 | Resolved | Fixed | b38 |
This bug asks to examine hijra-config-umalqura.properties files under ${java.home}/lib and understand if it is a configuration and whether it should be a resources file (in resources.jar).
The motive for this bug is the modular JDK where we need the flexibility to put anything that is module-private into a module-private location. In this case it would appear that the above files are not a supported interface and so should move to a location that should be read as resources.
The motive for this bug is the modular JDK where we need the flexibility to put anything that is module-private into a module-private location. In this case it would appear that the above files are not a supported interface and so should move to a location that should be read as resources.
- backported by
-
JDK-8082001 Read hijrah-config-umalqura.properties as a resource
-
- Resolved
-
- relates to
-
JDK-8049930 Move configuration files from ${java.home}/lib directory to ${java.home}/conf
-
- Resolved
-
-
JDK-8048123 Replace calendars.properties with another mechanism to specify a new Japanese calendar era
-
- Resolved
-
-
JDK-8039317 Read currency.data as a resource
-
- Closed
-