Add projects attribute to Weaver to filter out dependencies by project names #179
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.
In the
.yaml
file we currently support the project name:Now the weaver annotations will support the field
projects
to be able to limit which project the dependency is associated with.The annotation will look like this:
or this:
Since this is a
String
based field without autocomplete, typos may occur. To support this, I've added in build time logging (which is only printed out If theprojects
attribute is used):