feat: Scan Maven Plugins#5001
Conversation
|
@mprins thanks for the suggestion! |
aikebah
left a comment
There was a problem hiding this comment.
Reviews that should be addressed before merge in my view are :
https://github.com/jeremylong/DependencyCheck/pull/5001/files/fdc8896ec749c8f865e47ed529e58affa9bc7e0d#r1020950469
…encyCheckMojo.java Co-authored-by: Mark Prins <[email protected]>
…encyCheckMojo.java Co-authored-by: Hans Aikema <[email protected]>
…encyCheckMojo.java Co-authored-by: Hans Aikema <[email protected]>
…encyCheckMojo.java Co-authored-by: Hans Aikema <[email protected]>
|
@aikebah I think I'm good with the 8.0.0 PRs now. Planning on spending this week integrating the 8.0.0 PRs and testing so we can finally get these released. Please let me know if you see any additional issues/concerns. |
aikebah
left a comment
There was a problem hiding this comment.
See review, think we should stay on the safe side with internal Maven vars.... with that integrated all looks good to me
…encyCheckMojo.java Co-authored-by: Hans Aikema <[email protected]>
|
@jeremylong I'll leave the merge-sequence decision up to you.... my gut feel would be first the Known exploited and then the maven plugin would be the easiest to resolve any emerging merge conflicts |
|
Based on this dependency-check-sonar-plugin#748 Is there a way to disable that field or do we have to wait for it to be fixed? |
Fixes Issue #4035
Adds the ability to scan the plugins of a Maven project (via the org.owasp:dependency-check-maven plugin - not the CLI).
includedByto the HTML, XML, and JSON reports when scanning with the Maven Plugin.includedByis the root of the dependency tree (i.e. if a transitive dependency is scanned, theincludedBywill be a direct dependency). Note that when using the maven pluginincludedBywill be added even when plugins are not scanned.