Repository navigation
[MDEP-480] Add overWriteFiles to keep existing files when unpacking - #1794
Merged
slachiewicz merged 2 commits intoNov 14, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds
overWriteFiles(user propertymdep.unpack.overWriteFiles, defaulttrue) tounpack,unpack-dependenciesand eachartifactItem. Withfalse, an entry whose target file already exists, after thefileMappersare applied, is skipped whatever the timestamps, so an unpack afterprocess-resourceskeeps the filtered resources and only adds missing files. The existingoverWrite*options still decide per artifact whether to unpack at all. Single-file archives (gzip, xz, snappy, zstd) are not affected.Fixes #917
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
check one of the following: