JDK-8048124 : Read hijrah-config-umalqura.properties as a resource
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.time
  • Affected Version: 9
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2014-06-25
  • Updated: 2017-05-17
  • Resolved: 2014-10-28
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 b38Fixed
Related Reports
Relates :  
Relates :  
Relates :  
Description
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.
Comments
This has been reviewed on the core-libs-dev and will go into jdk9/dev in due course. There aren't any changes required specifically for the modular image so I will drop the bertha label from this issue.
28-10-2014

If the plan is to eliminate or move these to resource files then I think we can drop the "bertha" label from this issue. To Chris' point then if we are retaining the properties files as source files but not user-editable configuration files then they will need a new home in the src tree.
17-10-2014

There are currently two source files in the jdk repository that are incorrectly located in the 'conf' directory. jdk/src/java.base/share/conf/calendars.properties jdk/src/java.base/share/conf/hijrah-config-umalqura.properties The only files that should be in the source conf directory are files that are intended to be user editable, these are not, and therefore should be moved. As part of this work these files should be moved to a suitable location in the source tree that matches there intended location in the built artifact.
17-10-2014

It seems unlikely that we need to add new Islamic calendars between updates. So I think the function of the calendar.properties file can be removed. The individual Islamic calendars can be hard coded in HijrahCalendar. Each calendar does have a data file which will be treated as a resource. Initially, there is only one.
05-10-2014

Any update on this? We need to establish if is supported to edit hijra-config-umalqura.properties or not. This is so that we have a definite list of user-editable configuration files to move to the conf directory.
04-10-2014