org.owasp.dependencycheck.exception.NoDataException: No documents exist

When attempting to run mvn dependency-check:check I got the following error message/stacktrace in the log:

Jan 11, 2015 8:12:01 PM org.owasp.dependencycheck.Engine analyzeDependencies
SEVERE: No documents exist

Unable to continue dependency-check analysis.
Jan 11, 2015 8:12:01 PM org.owasp.dependencycheck.Engine analyzeDependencies
FINE: null
org.owasp.dependencycheck.exception.NoDataException: No documents exist
        at org.owasp.dependencycheck.Engine.ensureDataExists(Engine.java:541)
        at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:352)
        at org.owasp.dependencycheck.maven.CheckMojo.runCheck(CheckMojo.java:87)
        at org.owasp.dependencycheck.maven.BaseDependencyCheckMojo.execute(BaseDependencyCheckMojo.java:340)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)

I can attach more/the whole log if you want.

I have seen this issue before, and also saw some previous bug reports on it, but they suggested the issue had been fixed in newer releases.

I am now able to trigger in my local clone of the DependencyCheck repo. I don’t know the proper steps for how to trigger this issue and thhe problem may have occured earlier revision, but I am able to reproduce it in f8092da5faa1fa5cd56afa87f58b7ad4cb7c52b0 (the only modification I’ve done is add the dependency-check plugin version 1.2.8 to the root pom).