JDK-8140760 : Create a README file describing how to write os specific property files
- Type: Enhancement
- Component: hotspot
- Sub-Component: test
- Affected Version: 9
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- Submitted: 2015-10-29
- Updated: 2017-12-06
- Resolved: 2017-12-06
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 11 |
|---|
11Resolved  |
Related Reports
|
Duplicate :
|
Description
Using a mechanism of property files for describing services is good enough: - easy to support - flexible: allows to describe whatever we need - human readable One problem with using it I bumped into - some magic is used, like native.pattern = %p To get things better: - a readme file should be provided - in all property files that readme file should be mentioned - the readme file should: * general description of what should be provided os.properties files * list all "fields" supported by mechanism: args, app, pattern, etc * a few examples given
Comments
|