fix regression: only skip jar-scanning completely if scanSet is empty #264
Conversation
This file contains 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
martin-g
approved these changes
Mar 20, 2020
|
Fixed with 9c6563b |
Hm, that would ignore the case, that |
|
I hadn't seen this PR at all as there was a BZ there already and it didn't mention it. |
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.
The commit 21d08e1 introduced a regression to the behavior of jar-scanning. Since version 9.0.31 it skips all jars, if a wildcard is found in the skipSet - no matter the content of the scanSet!
The documentation for
jarsToScanclearly states:This PR restores this behavior by also respecting the "jarsToScan".