JDK-8039317 : Read currency.data as a resource
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util:i18n
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-04-04
  • Updated: 2019-08-24
  • Resolved: 2014-06-26
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.
JDK 9
9 b22Fixed
Related Reports
Relates :  
JDK-8048123 - Replace calendars.properties with another mechanism to specify a new Japanese calendar era
Relates :  
JDK-8048124 - Read hijrah-config-umalqura.properties as a resource
Relates :  
JDK-8039362 - Read content-types.properties as a resource
Description
--- Original description ---
This bug asks to examine the i18n data/properties files under ${java.home}/lib and understand if they are configurations and whether they should be resources files (in resources.jar).

lib/calendars.properties
lib/currency.data
lib/hijrah-config-umalqura.properties

Perhaps there are other files under ${java.home}/lib for i18n not listed above.

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.
---

As I have separated issues for calendar.properties and hijrah-config-umalqura.properties as distinct issues, this issue intends to deal with currency.data file only. I also modified the title accordingly.
Comments
@Naoto - what do you mean by "have to be modifiable"? If we support customers changing these files then it is a supported interface. Maybe you the issue here is we are missing a means to override the configuration?
23-06-2014
Isn't the system property java.util.currency.data the supported way to do this now?
25-04-2014