You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by re...@apache.org on 2018/10/11 13:11:10 UTC
svn commit: r1843547 -
/jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Author: reschke
Date: Thu Oct 11 13:11:10 2018
New Revision: 1843547
URL: http://svn.apache.org/viewvc?rev=1843547&view=rev
Log:
update dependency-check-maven version
Modified:
jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Modified: jackrabbit/site/trunk/src/site/markdown/creating-releases.md
URL: http://svn.apache.org/viewvc/jackrabbit/site/trunk/src/site/markdown/creating-releases.md?rev=1843547&r1=1843546&r2=1843547&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Thu Oct 11 13:11:10 2018
@@ -57,7 +57,7 @@ Release management tasks
### Part I: up to the release vote
1. Consider checking the CVE database for vulnerabilities in dependencies,
- using `mvn org.owasp:dependency-check-maven:3.2.1:aggregate` (first run will be slow because CVE
+ using `mvn org.owasp:dependency-check-maven:3.3.2:aggregate` (first run will be slow because CVE
databases are downloaded and parsed). If dependencies need action, open tickets and make sure they
are marked as candidate backports where applicable.
2. Make sure that an appropriate version for the release is entered in Jira