| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8288579 | 20 | Brian Burkhalter | P5 | Resolved | Fixed | b03 |
A DESCRIPTION OF THE PROBLEM :
Documentation for Files.copy with REPLACE_EXISTING flag says that replacement happens if target is not empty directory. It should be when it's empty instead since DirectoryNotEmptyException is raised otherwise.
Documentation for Files.copy with REPLACE_EXISTING flag says that replacement happens if target is not empty directory. It should be when it's empty instead since DirectoryNotEmptyException is raised otherwise.
- backported by
-
JDK-8288579 (fs) Files.copy description of REPLACE_EXISTING is hard to read
-
- Resolved
-
- csr for
-
JDK-8288326 (fs) Files.copy description of REPLACE_EXISTING is hard to read
-
- Closed
-
