Fixes mojohaus#123: add scope filtering #915
Merged
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
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.
This implements one of the features requested in #123 : filtering of artifacts based on their scope.
It adds a scope property to the plugin configuration.
When this is set, only artifacts matching this scope (or ones implied in the maven scope hierarchy) are included.
I made a test for the compare-dependencies goal as it is here that I intend to use it, but it applies to all the goals.
My need it to run comparison only on
compiledependencies (excluding the tests one that are included in the comparison by default)(I tried this PR a long time ago as #334 but it went stale and I did not follow up on it at the time)