-
Notifications
You must be signed in to change notification settings - Fork 13
Keep direct dependencies whose scope or exclusions differ from the transitive one #188
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
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
3257855
Keep direct dependencies whose scope or exclusions differ from the tr…
timtebeek a274e06
Simplify test POMs: drop XML declaration and project attributes
timtebeek 6890da4
Extract handleGradle/handleMaven and trim comments
timtebeek 2ea65bb
Rename getCompatibleTransitives to getCompatibleGradleTransitives
timtebeek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did we end up dropping the differing scopes check for Maven and now only use the broader gradle scopes? I may have missed something here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question — the short version is that Maven still checks scope, it just does it differently, so the widening helper is no longer needed there.
Maven (
handleMaven): each direct dependency is now evaluated against transitives collected under its own declared scope, matched exactly:The scan phase keys the parent's transitives by the parent's own declared scope as well, so it's an apples-to-apples comparison.
getBroaderMavenScopesonly existed because the old code iteratedmaven.getDependencies()resolution buckets — where acompiledep also shows up in theruntime/testbuckets — and keyed transitives by bucket; that mismatch is what needed reconciling. Keying by declared scope removes the need.This is also a deliberate behavior change: we no longer treat a broader-scoped transitive as covering a narrower-scoped direct declaration, since that changes the effective classpath (e.g. dropping a direct
runtimedep because acompiletransitive provides it). It's locked in bykeepsRuntimeTomcatEmbedCoreWhenTransitiveIsCompileScopedandkeepsDirectCompileTomcatEmbedCoreWhenProviderIsProvidedScoped.Gradle (
handleGradle): still usesgetCompatibleTransitives/getBroaderGradleScopesbecause there transitives are keyed by configuration name, and Gradle configurations genuinely inherit (testImplementation→implementation→api). A dependency in one configuration legitimately sees transitives from the configurations it extends, so we still walk those. Maven's flat declared-scope model has no such inheritance, so exact-scope matching is sufficient.Happy to add a code comment making the Maven-vs-Gradle asymmetry explicit if that would help.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe just a method rename to
getCompatibleGradleTransitivesor something like that. I guess I missed that it was no longer called by thehandleMaventhat was extracted.