-
-
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
New SAXParseException in DependencyCheck v3.3.0 #1400
Comments
For completeness, this is what the console output looks like for the jenkins plugin v3.3.0:
|
I have similar stacktraces for a different POM in 3.3.0, resolved by falling back to 3.2.1 |
So I am having problems re-producing this bug. Any chance you can run:
Then provide the log output? |
I'm using Gradle (4.9) as a build tool This
Which produces this (no stack trace for the 'Content is not allowed in prolog.' which actually appears on stderr)
|
This is the same task, but using 3.2.1
|
My original report, where the specific parse errors came from plexus-utils and mailapi, was also based on usage of swagger-codegen via org.zalando.stups:swagger-codegen-common.
Thus, using maven-dependency-plugin:3.0.0:tree...
Do you need any additional info? |
Thanks @jeremylong - 3.3.1 definitely fixes this for me |
Conflicts: core/src/test/java/org/owasp/dependencycheck/xml/pom/PomParserTest.java
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. |
Dependency-Check CLI v3.3.0 is generating SaxParseException that did not occur with v3.2.1 (at least based on usage in Dependency-Check Jenkins plugin).
I am not a developer but I am wondering if this is a regression introduced by (v3.3.0) fix for #1016.
From Dependency-Check CLI log:
I can attach a full log if need be.
Two problem POMS are:
and:
Both POM files include a copyright statement as a comment at the start... not sure if that is the problem. See:
http://central.maven.org/maven2/org/codehaus/plexus/plexus-utils/3.0.24/plexus-utils-3.0.24.pom
The text was updated successfully, but these errors were encountered: