Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure multi-module SBT plugins respect excludedModules setting #199

Merged
merged 3 commits into from
Apr 23, 2024
Merged

Ensure multi-module SBT plugins respect excludedModules setting #199

merged 3 commits into from
Apr 23, 2024

Conversation

alejandrohdezma
Copy link
Contributor

On alejandrohdezma/sbt-github#516 I noticed that sbt-version-policy wasn't respecting the versionPolicyIgnoredInternalDependencyVersions setting on multi-module SBT plugins.

This was due to a mismatch on the information under report.modules & excludedModules in the DependencyCheck.modulesOf method. On SBT plugin builds report.modules contains modules without the scala version suffix, while excludedModules contains them with the suffix.

The fix introduced in this PR checks for the presence of sbtVersion and scalaVersion "extra" attributes in the ModuleID and creates the appropriate cross-version string name in that case.

@julienrf julienrf self-assigned this Apr 7, 2024
alejandrohdezma and others added 2 commits April 23, 2024 10:11
…place as other types of modules and add a specific test for that
@julienrf julienrf merged commit c8c8794 into scalacenter:main Apr 23, 2024
2 checks passed
huajiang-tubi pushed a commit to adRise/sbt-version-policy that referenced this pull request Jun 25, 2024
…alacenter#199)

* Ensure multi-module SBT plugins respect `excludedModules` setting

Co-authored-by: Julien Richard-Foy <julien@richard-foy.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants