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 2021/08/26 11:36:10 UTC
svn commit: r1892616 -
/jackrabbit/site/trunk/src/site/markdown/creating-releases.md
Author: reschke
Date: Thu Aug 26 11:36:10 2021
New Revision: 1892616
URL: http://svn.apache.org/viewvc?rev=1892616&view=rev
Log:
update version of Dependency Check Maven Plugin
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=1892616&r1=1892615&r2=1892616&view=diff
==============================================================================
--- jackrabbit/site/trunk/src/site/markdown/creating-releases.md (original)
+++ jackrabbit/site/trunk/src/site/markdown/creating-releases.md Thu Aug 26 11:36:10 2021
@@ -60,7 +60,7 @@ Release management tasks
1. Check the CI status of the project ([Jackrabbit Jenkins](https://ci-builds.apache.org/job/Jackrabbit/))
2. Consider checking the CVE database for vulnerabilities in dependencies,
- using `mvn org.owasp:dependency-check-maven:6.0.0:aggregate` (first run will be slow because CVE
+ using `mvn org.owasp:dependency-check-maven:6.2.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.
3. Make sure that an appropriate version for the release is entered in Jira