JDK-8059976 : Convert JavacFileManager to use java.nio.file internally
- Type: Enhancement
- Component: tools
- Sub-Component: javac
- Affected Version: 9
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-10-08
- Updated: 2022-03-16
- Resolved: 2015-12-07
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 b97Fixed  |
Related Reports
|
Duplicate :
|
|
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The java.nio.file API (and related zipfs file system) provide a better, more functional, and simpler API than the mix of java.io.File, java.util.JarFile, and private internal support for reading zip files currently found in javac. We should convert JavacFileManager to use java.nio.file internally. See JDK-8059977 for the related bug, regarding the use of java.nio.file in the public API (i.e. StandardFileManager.)
Comments
|