[binderator] Allow extraDependencies to specify an excludedDependency.
#780
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.
Context: #773
We have an artifact that specifies a dependency that we cannot automatically figure out the version to (likely due to unsupported parent POMs).
We would like to work around this by ignoring the bad dependency with
excludedRuntimeDependencies, and then adding it back withextraDependencies, which will use the dependency version specified in the config file:However, the way we currently process this, the dependency gets excluded because the "excludes" are processed after the "extras".
Rework the logic so we run the "excludes" first and then add in the "extras".