Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
POM missing warning for v2.12.2
See original GitHub issueI 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
Issue Analytics
- State:
- Created 3 years ago
- Comments:26 (19 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@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.