jackson-jaxrs-providers: POM missing warning for v2.12.2
I just updated to v2.12.2 and got these warning while building.
Downloading from central: https://repo.maven.apache.org/maven2/com/fasterxml/jackson/jaxrs/jackson-jaxrs-base/2.12.2/jackson-jaxrs-base-2.12.2.pom [WARNING] The POM for com.fasterxml.jackson.jaxrs:jackson-jaxrs-base:jar:2.12.2 is missing, no dependency information available Downloading from central: https://repo.maven.apache.org/maven2/com/fasterxml/jackson/datatype/jackson-datatype-jaxrs/2.12.2/jackson-datatype-jaxrs-2.12.2.pom [WARNING] The POM for com.fasterxml.jackson.datatype:jackson-datatype-jaxrs:jar:2.12.2 is missing, no dependency information available Downloading from central: https://repo.maven.apache.org/maven2/com/fasterxml/jackson/jaxrs/jackson-jaxrs-json-provider/2.12.2/jackson-jaxrs-json-provider-2.12.2.pom [WARNING] The POM for com.fasterxml.jackson.jaxrs:jackson-jaxrs-json-provider:jar:2.12.2 is missing, no dependency information available Downloading from central: https://repo.maven.apache.org/maven2/com/fasterxml/jackson/datatype/jackson-datatype-jsr353/2.12.2/jackson-datatype-jsr353-2.12.2.pom [WARNING] The POM for com.fasterxml.jackson.datatype:jackson-datatype-jsr353:jar:2.12.2 is missing, no dependency information available
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 26 (19 by maintainers)
Commits related to this issue
- Remove Jakarta bundle fix added in #136 to try to fix #138 — committed to FasterXML/jackson-jaxrs-providers by cowtowncoder 3 years ago
- Remove Jakarta bundle fix added in #136 to try to fix #138 (#139) Remove Jakarta bundle fix added in #136 to try to fix #138 — committed to FasterXML/jackson-jaxrs-providers by cowtowncoder 3 years ago
- Manual merge of #138 (wrt pom.xml) — committed to FasterXML/jackson-jaxrs-providers by cowtowncoder 3 years ago
- Manual merge of pom.xml (wrt #138) — committed to FasterXML/jackson-jaxrs-providers by cowtowncoder 3 years ago
@megglos My guess at this point is that I’ll probably have to do 2.12.2.1 micro-path for JAX-RS and jsr-353 first, as a sort of hotfix. And then once everything is verified, settled, 2.12.3, quite soon after. I am not sure it will be feasible to retrofit 2.12.2 that got out due to the way Maven Central syncing works.
@ilgrosso yes, every artifact that has javax->jakarta classifier has this problem unfortunately, it seems.
Suspecting this is due to #136, since I noticed that the
jackson-datatype-jsr353:https://repo.maven.apache.org/maven2/com/fasterxml/jackson/datatype/jackson-datatype-jsr353/2.12.2/
is similarly broken. I do not understand why Nexus allows closing and releasing of such artifact set (seems like a broken set); and also why is build itself broken… What I horrible fucking mess. Thank you for reporting it, I just hate when things get corrupt.
Confirmed this has resolved our build issues. Thank you @cowtowncoder !
Update: I re-ran release up to upload, but no close with Nexus staging plugin; information added to https://issues.sonatype.org/browse/MVNCENTRAL-6595 . No problem reported on client side logs, seems to include pom, so would seem likely Nexus dropping poms (but obviously not proof; release plugin could be dropping it).