Ensure multi-module SBT plugins respect excludedModules
setting
#199
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.
On alejandrohdezma/sbt-github#516 I noticed that
sbt-version-policy
wasn't respecting theversionPolicyIgnoredInternalDependencyVersions
setting on multi-module SBT plugins.This was due to a mismatch on the information under
report.modules
&excludedModules
in theDependencyCheck.modulesOf
method. On SBT plugin buildsreport.modules
contains modules without the scala version suffix, whileexcludedModules
contains them with the suffix.The fix introduced in this PR checks for the presence of
sbtVersion
andscalaVersion
"extra" attributes in theModuleID
and creates the appropriate cross-version string name in that case.