Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Bug in Maven Central Analyzer
See original GitHub issueI’m not positive yet if this is an issue on my end or if it’s a legitimate problem, the Maven Central analyzer has been throwing errors, it’s getting a 400 back from Maven Central. I piped the results through Fiddler to take a look at what’s going on, if I put the URL into Chrome it works, so I realized that the difference is that Chrome is URL encoding the quotation marks.
https://search.maven.org/solrsearch/select?q=1:"<sha1>"&wt=xml is what Dependency Check is trying to use.
https://search.maven.org/solrsearch/select?q=1:%22<sha1>%22&wt=xml works.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:58 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
3.0.2 has been mostly released - gradle, maven, ant, and CLI have been published - it just takes time to cycle through Central.
Jenkinsandbrewwill be released hopefully later today… Sorry for the inconvenience - but this project isn’t corporate sponsored and I do not believe any of the core contributors work on dependency-check as part of their day job.I’m still getting the [ERROR] Could not connect to Central search. Analysis failed. intermittently. I’m using version 3.1.2 (latest version as of the moment) and sometimes it works, sometimes not. I’m not changing anything in my config and still getting the error randomly.
Has anyone experienced this? Is disabling centralAnalyzer the only option I have? Thanks.