Removing IOException when using ZIP with "overwrite: true", and the ZIP doesn't currently exist #82
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
Currently, when running a pipeline creating a ZIP and specifying "overwrite: true", if the destination file doesn't exist, it will throw an IOException. I've run into this issue often when running a pipeline for the first time, or after clearing a workspace.
The original pull request (#76) checked if the ZIP existed prior to attempting to delete, however this was lost after feedback encouraging converting to NIO2 file APIs, where it now throws an IOException. This pull request changes the functionality to be more like the original.
Return value of Files.deleteIfExists is ignored, as it indicates if the file existed or not, and for overwriting I don't believe we mind either way.
Thanks