JDK-6876000 : (fs spec) Path.createXXX should make it clear that it doesn't create parent directories
- Type: Bug
- Component: core-libs
- Sub-Component: java.nio
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2009-08-26
- Updated: 2010-12-10
- Resolved: 2010-12-10
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 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
It was observed on the nio-discuss mailing list that Path's createFile, createDirectory, createSymbolicLink ... don't make it clear if they create missing parent directories. They don't of course, but this should be made clearer so that readers of the javadoc are in no doubt.
Comments
|