JDK-8133777 : Use file based persistence for history instead of preferences
- Type: Sub-task
- Component: core-libs
- Sub-Component: jdk.nashorn
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-08-18
- Updated: 2015-09-10
- Resolved: 2015-08-18
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 |
|---|
9 b79Fixed  |
Description
jjs supports Ctrl-C termination as well as shutdown functions like "quit" and "exit". In addition, user can also call java.lang.System.exit directory. Because of this, we can't enforce orderly shutdown to save command history before process termination. Using shutdown hook with preferences API has issues - perhaps because preferences API itself uses shutdown hooks to flush the changes! Besides simple file based command line history => user can open with other editors and offline edit the history as well.