Fixed ignoring of subpaths inside a repository #33
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.
Use-Case: Explicitly matching a subpath inside a repository for ignore or moving to another repository like that:
Problem: When there is a change to /trunk/project/ (e.g. changing a property), recursiveDumpDir always dumped the complete subpath to the parent repo, ignoring the rules of subpaths.
This pull request implements rule matching also for recursiveDumpDir.