JDK-7108668 : allow Log to be initialized and used earlier
- Type: Bug
- Component: tools
- Sub-Component: javac
- Affected Version: 8
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2011-11-05
- Updated: 2012-11-02
- Resolved: 2012-03-02
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 8 |
|---|
8 b15Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
There's currently a circularity in javac initialization: bad options on the command line need to be reported somewhere, and some options say where to report diagnostics. The current resolution involves separate resource bundles and separate mechanisms to access them, in Log and Main. By allowing Log to be initialized earlier, and updated as needed, we should be able to simplify this complexity.
Comments
|