Jeremy Long

Should be resolved with https://github.com/dependency-check/dependency-check-gradle/pull/286 - which will be released soon.

I just pieced together what is happening. The warning can obviously be ignored.

Sorry this took me so long to get to: https://github.com/dependency-check/dependency-check-gradle/pull/287

Others that have reported this issue have confirmed running `./gradlew dependencyCheckPurge` resolves the issue.

Would using an init-script, such as described in [odc/issues#4044](https://github.com/jeremylong/DependencyCheck/issues/4044#issuecomment-1030828651), work?

approved

This would be a good addition.

To improve performance checkout https://jeremylong.github.io/DependencyCheck/data/cache-action.html and https://jeremylong.github.io/DependencyCheck/data/cacheh2.html. Also, if you are using a single API key for all 50 scans being run nightly and you are building the database from...

I've never had an issue with the reliability of pulling data from a cache. Possibly memory issues in some env? Another option would be to use a single node, even...

This is discussed here: https://jeremylong.github.io/DependencyCheck/data/cacheh2.html