Simple issues
Run Detect with
--logging.level.detect=DEBUG(the default logging level, INFO, is insufficient for troubleshooting) and read through the entire log for clues.For additional detail, run with
--logging.level.detect=TRACE.Detect typically runs package manager commands or build tool commands similar to commands used in your build. When run by Detect, those commands (as well as the environment in which they run) need to be consistent with your build, and it's important to verify that they are. For example, the Gradle detector defaults to running ./gradlew dependencies if it finds the file ./gradlew. If your build runs a different Gradle command or wrapper such as /usr/local/bin/gradle, use property detect.gradle.path to tell Detect to run the same Gradle command that your build runs. Check the DEBUG log for the package manager commands that Detect is running, and compare them to the commands your build runs.
More complex issues
For more complex issues, including any issue that requires help from Black Duck Support, refer to Diagnostic mode.