-
Notifications
You must be signed in to change notification settings - Fork 380
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
Transitive dependency support for Maven pom.xml #1002
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1002 +/- ##
==========================================
+ Coverage 64.47% 65.06% +0.59%
==========================================
Files 148 149 +1
Lines 12088 12250 +162
==========================================
+ Hits 7794 7971 +177
+ Misses 3843 3832 -11
+ Partials 451 447 -4 ☔ View full report in Codecov by Sentry. |
<dependencies> | ||
<dependency> | ||
<groupId>junit</groupId> | ||
<artifactId>junit</artifactId> | ||
<version>4.12</version> | ||
<scope>test</scope> |
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.
@michaelkedar I think we should fix the resolver not to ignore test
dependencies. junit:junit
is not in the resolve graph. :(
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.
LGTM!
Issue google#35 In this PR, the new Maven extractor invokes Maven resolver to compute the transitive dependencies of a Maven pom.xml. Since managed dependencies are not actually being depended on, they are not in the resolved dependency graph, and thus they are not included in the scan results.
Issue #35
In this PR, the new Maven extractor invokes Maven resolver to compute the transitive dependencies of a Maven pom.xml.
Since managed dependencies are not actually being depended on, they are not in the resolved dependency graph, and thus they are not included in the scan results.