Error scanning after latest update

[clj-holmes]

Error scanning after latest update

[seancorfield]

Latest version? 4.1.3 or 5.0.0

NIST has required users of its NVD database to switch to the new API, from the old data feeds. 4.1.3 still uses the data feeds, 5.0.0 uses the API. To use the API, you need a key per the README, however there's a small bug in how the clj-watson.properties file is read (see #43).

You can work around it in 5.0.0 by specifying -w and the same relative path to where the file would be on the classpath.

Or you can depend on :git/sha "76b687f3eb807ab55632c69ef2c011886513efef" which is the PR that fixes it and will be part of the 5.0.1 release, once @mthbernardes either approves my PRs or removes the requirement for at least one reviewer (since none of the reviewers are currently responding to PR review requests).

Once the PR/merge/push process is simplified, I'll be taking the project over. I started my own fork to create the 5.0.0 release but @mthbernardes and I agree that keeping it under clj-holmes would be better.

[puredanger]

I had switched to 5.0.0. I saw the API stuff and do have a clj-watson.properties file with an api key on the classpath. It did not seem like the error I got was related to the API stuff though?

[puredanger]

I switched to the sha above and got the same error.

[seancorfield]

You may have to rm -rf /tmp/db to get a clean database (cache) setup at this point.

[seancorfield]

I'll add a Troubleshooting section to the README with this information in it (and maybe other things).

[seancorfield]

The README already mentioned the /tmp/db folder but only in passing as part of the DependencyCheck section, so I added a note to the Quick Start about deleting it, if it seems to be causing problems.