Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Andy Wilkinson opened SPR-15845 and commented
In 4.3, copyRecursively would replace existing files. In 5.0, the move to Files.copy means that existing files are no longer overwritten and the copy fails with a FileAlreadyExistsException.
I wonder if this change was intentional (and could perhaps be mentioned in the javadoc), or if using StandardCopyOption.REPLACE_EXISTING would be appropriate.
Affects: 5.0 RC3
Referenced from: commits fabc9c2
The text was updated successfully, but these errors were encountered:
Juergen Hoeller commented
Sorry, something went wrong.
No branches or pull requests