-
Notifications
You must be signed in to change notification settings - Fork 0
allow for coincidental versions #7
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
Open
lithium147
wants to merge
6
commits into
main
Choose a base branch
from
feature/coincidental-versions
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
204a18a
allow for coincidental versions
lithium147 abc6875
comment about uniqueness approach
lithium147 19e67f8
Merge branch 'main' into feature/coincidental-versions
lithium147 ea3db73
Merge branch 'main' into feature/coincidental-versions
lithium147 4b8cc34
Merge branch 'main' into feature/coincidental-versions
lithium147 4c8093d
Merge branch 'main' into feature/coincidental-versions
lithium147 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
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
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.
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.
🔴 Grouping by uniqueness() causes false-positive redundant-property violations when a shared property is used across different groupIds
The change from
groupingBy(Artifact::getEffectiveVersion)togroupingBy(Artifact::uniqueness)(whereuniqueness()returnsgroupId:effectiveVersion) breaks the detection of shared properties used across different groupIds.Consider two dependencies from different groupIds that both reference the same property:
withDependency("com.a", "artifact-a", "common.version", "1.0.0")andwithDependency("com.b", "artifact-b", "common.version", "1.0.0"). Previously these were grouped together under effective version1.0.0(2 artifacts, both using the property → no violation). Now they form two separate groups (com.a:1.0.0andcom.b:1.0.0), each with 1 artifact that hashasImplicitVersion() == true, which triggersredundantPropertyViolationfor each — a false positive, since the property IS legitimately shared.Concrete example of the false positive path through scan()
For each single-artifact group where propertyCount == 1 (line 89),
redundantPropertyViolationis called. The property is actually used in 2 places, but the grouping hides this. The fix should consider a uniqueness key that avoids coincidental version matches (the original problem) without breaking shared property detection across groupIds.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.