Quitting dependency-check during an update leaves stale lock file

Launch dependency-check and, while it is performing a database update, press CTRL-C to quit the process. Immediately launch dependency-check again and the tool hangs after printing:

[dependency-check] SLF4J: Class path contains multiple SLF4J bindings.
[dependency-check] SLF4J: Found binding in [jar:file:/Users/chris/packages/dependency-check-ant/dependency-check-ant.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[dependency-check] SLF4J: Found binding in [jar:file:/Users/chris/packages/dependency-check-ant/lib/dependency-check-ant-3.0.2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
[dependency-check] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
[dependency-check] SLF4J: Actual binding is of type [org.owasp.dependencycheck.ant.logging.AntLoggerFactory]

A bit of Googling led me to this issue: https://github.com/jeremylong/DependencyCheck/issues/1000

Deleting the lock file allowed me to resume my work.

It would be nice if dependency-check would clean-up after itself in case it gets interrupted. (If possible). Otherwise, perhaps https://github.com/jeremylong/DependencyCheck/issues/1000 is enough to mitigate this problem.

I happen to be using the Apache ant task, if that makes any difference.

(Thanks for the great tool!)

[jeremylong]

Thanks for reporting this issue - I got to learn something new regarding shutdown hooks. This makes ODC much more stable!

[jeremylong]

I’ll do some research on this one - some changes that need to be made are updating the error reporting per issue #1000 and updating the purge task (and related) to remove the lock file.