Jeremy Long

@EugRomanchenko try: ```gradle dependencyCheck { format='ALL' data { directory='/home/gradle/project/dependency-check-data' } } ```

@spanierm Your last gist shows a success full creation of the database - yet you said it still fails? ``` 20:06:05.408 [DEBUG] [org.gradle.launcher.daemon.client.DaemonClient] Received result Success ``` The update of...

I believe `-Ddata.directory=/home/gradle/project/dependency-check-data` would work.

The option already exists (`failOnError`). See the [ODC gradle documentation](https://jeremylong.github.io/DependencyCheck/dependency-check-gradle/configuration.html) for more info. ```groovy dependencyCheck { failOnError = false } ```

Just getting back to this - instead of a new `ignoreBuildStatus` wouldn't just setting `failBuildOnCVSS=11` work to disable this build failure?

The plugin is compatible - ODC is just pulling in the scopes within the build. When you use gradle 7+ the scopes it is complaining about won't be present so...

Any chance you can share you dependency check configuration in your `build.gradle`?

This would not be a trivial implementation. Most of the information used to suppress findings is not known until well after the dependencies for each project/scope are collected.

Fail on error is intended to control the failure mode for non-fatal errors. If the NVD is not available for download ODC really can't perform any analysis if we don't...

In this case - my guess is that the cache may not be working correctly as the error thrown only occurs when no data exists in the database (see [Engine.java#L656-L660](https://github.com/jeremylong/DependencyCheck/blob/cc387b6d039e19d004866d4c67178d631c405693/core/src/main/java/org/owasp/dependencycheck/Engine.java#L656-L660))....