-
-
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
bad jackson version #4280
Comments
2.13.2.2 has been released and works when manually imported. Can a bumped version of this project be released? |
I don't see this being fixed.
When I change the version to 7.0.3 I get:
https://plugins.gradle.org/plugin/org.owasp.dependencycheck does not show release 7.0.3. |
@pkubowicz - that is because you didn't use 7.0.3. I was interrupted during the release process this morning and only just now was able to push the updated version. |
Hi @jeremylong, I appreciate that this issue is closed, I just noticed that the build of dependency check gradle failed due to the jackson-databind invalid metadata issue in 2.13.2.1 My apologies if you are already aware of this but jackson released a new version of the bom (jackson-bom:2.13.2.20220328) which addresses the issue with jackson-databind by referencing the newly released 2.13.2.2. Details are here: |
@jrmcdonald thanks - I guess I'll be release 7.0.4 tomorrow.... ugh. |
the release build worked locally... |
No worries, it's been confusing trying to keep up with the versions. As another FYI, the jackson maintainers have stated that they've published a version 2.13.2.1 of jackson-bom, which should fix the the issue for 2.13.2.1 of jackson-databind. FasterXML/jackson-bom#52 (comment) It doesn't seem to be on maven yet (at least as of 09:50 BST). |
Describe the bug
A clear and concise description of what the bug is.
Could not resolve all artifacts for configuration ':classpath'.
Version of dependency-check used
The problem occurs using version 7.0.2 of the gradle (cli, gradle plugin, maven plugin, etc.)
Log file
Could not resolve all artifacts for configuration ':classpath'.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error when executing
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: