Gradle module metadata for 2.13.2.1 references non-existent jackson-bom 2.13.2.1
See original GitHub issueDescribe the bug See: https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.13.2.1/jackson-databind-2.13.2.1.module
The Gradle module metadata for the 2.13.2.1 release contains:
{
"group": "com.fasterxml.jackson",
"module": "jackson-bom",
"version": {
"requires": "2.13.2.1"
},
"attributes": {
"org.gradle.category": "platform"
},
"endorseStrictVersions": true
}
The jackson-bom
version that should be resolved (via jackson-base
) is 2.13.2.20220324
. Everything is fine consuming jackson-databind from Maven, but from Gradle it is currently broken in 2.13.2.1 due to this wrong metadata which causes Gradle to try and fail to resolve jackson-bom:2.13.2.1
as seen in this error:
Could not find com.fasterxml.jackson:jackson-bom:2.13.2.1.
This can also be seen in this failed build scan.
Version information Which Jackson version(s) was this for? 2.13.2.1
To Reproduce If you have a way to reproduce this with:
Add a dependency on jackson-databind
version 2.13.2.1 in a Gradle build and build the project. E.g.
dependencies {
implementation 'com.fasterxml.jackson.core:jackson-databind:2.13.2.1'
}
Expected behavior If reproduction itself needs further explanation, you may also add more details here.
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created a year ago
- Reactions:24
- Comments:35 (18 by maintainers)
Top GitHub Comments
Just released
jackson-databind:2.13.2.2
along with optionaljackson-bom:2.13.2.20220328
. This should have corrected GMM metadata, and be available from Maven Central soon (databind is there, bom on its way).I am hoping to get it done today. If not, tomorrow, and so forth. It all depends on my having time to do it that’s all. I wish my job was related to maintaining Jackson but this is not the case currently.