-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error org.owasp.dependencycheck.xml.pom.PomParseException with ojdbc7.jar analysis #1439
Comments
Checked the same situation in 3.2.0
|
Looks like it is related to this commit 10ea23c |
we should check something like:
and also here: And i guess PomUtils.analyzePOM also can be used in try-catch scenario, to not fail whole run if some pom.xml's will be not parsed like here #1016 |
Hello, I have same issue in my project. Dmitry, have you fix issue by yourself, or waiting to fix from Jeremy? |
@Kovshar-OS, I have reverted to use version 3.2.0 in our CI.
instead of CentralAnalyzer.java#L261 |
@Kovshar-OS, pull request with fixed issue, created |
Thanks for the PR! |
Workaround: just pass |
Unfortunately this is not possible when using the Jenkins plugin. |
I'm going to do a release next weekend (Sept 8-9th). |
Life happened - I should publish the next release the weekend of the 15th. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
After upgrading OWASP Dependency Check CLI 3.2.0 -> 3.3.1 Faced with error:
org.owasp.dependencycheck.xml.pom.PomParseException: Unable to parse pom ...
after adding logs found, that issue with ojdbc7.jar file.
Just for test, I have created directory with only this jar file and started /d/tmp/dependency-check/bin/dependency-check.bat --project "OJDBC" --scan "." --format ALL --log odc.log
main issue that it cannot find needed lib in Central Repository:
Full Log of scan you can find here: odc.log
The text was updated successfully, but these errors were encountered: