dependency-check 1.2.6 released!

159 views
Skip to first unread message

Jeremy Long

unread,
Nov 17, 2014, 6:03:50 AM11/17/14
to dependen...@googlegroups.com
All,

The dependency-check team is pleased to announce the release of 1.2.6! Aside from general code clean-up, several important changes are included in this release and I would highly recommend upgrading. The documentation site has been updated, the Command Line Interface (CLI) and ANT task are available on bintray, the Maven plugin and Ant task are available in Central, and the Jenkins plugin is available through Jenkins plugin management.

Please let us know if you have issues either by posting to the group or opening an issue.

Summary of changes:
  1. Fixed reported false positives.
  2. The Maven plugin now uses the dependencies GAV as declared in the project/POM being scanned (thanks Erik!).
  3. Resolved issue #156 to ensure consistent results rather then cycling removed and added issues in Jenkins.
  4. The CLI now accepts Ant style paths for the '--scan' argument.
  5. The CLI now accepts an '--exclude' argument that accepts Ant style exclusions.
  6. When using the CLI you can now specify a file name for the output file (as long as the --format is not set to ALL). The file extension must be xml when --format is set to xml or '.htm' or '.html' for either of the HTML formated reports.
  7. The Nexus Analyzer has been disabled and replaced with the Central Analyzer. If you specify a Nexus Pro URL in the configuration dependency-check will use the specified Nexus Pro server instead of using Central. The functionality between the two analyzers is identical; however, the very supportive people at Sonatype asked us to make this change - so please upgrade to use the Central Analyzer.
  8. Updated the URLs to download the NVD CVE data to use the gzip version. This has drastically decreased the time required to update the local cache of the NVD data. NOTE - if you are mirroring the NVD on your local network the original URLs to the XML files will work; but it is strongly advised that you change to using the gzip URLs. The current URLs can be obtained from the dependencycheck.properties file:  

Best Regards,

the dependency-check team
Reply all
Reply to author
Forward
0 new messages