Same maven coordinates but different content between maven central and jitpack.io

[jeremiehuchet]

I noticed that artifact com.github.java-json-tools:jackson-coreutils:2.0 doesn't have the same content in maven central and jitpack.io repository :

• maven central : https://repo1.maven.org/maven2/com/github/java-json-tools/jackson-coreutils/2.0/jackson-coreutils-2.0.pom
• jitpack.io : https://jitpack.io/com/github/java-json-tools/jackson-coreutils/2.0/jackson-coreutils-2.0.pom

It caused me trouble executing plugin org.openapi:openapi-generator-maven-plugin:5.1.1 on a project using artifacts from jitpack.io.
Repositories declared in the pom.xml takes precedence over maven central and the jackson-coreutils artifact from jitpack.io was fetch. This artifact depends on com.github.java-json-tools.jackson-coreutils:jackson-coreutils:2.0 (please note the different groupid) which seems unavailable neither in maven central nor jitpack.io.
As a workaround, I declared the maven central repository before the jitpack.io repository in my pom.xml.

It seems to me it is dangerous that the same artifact coordinates are used across different repositories with different artifact content.

Is this project managing deployments to jitpack.io ?

[marcoeig]

thanks for the workaround, took me a the whole morning to figure out what's causing my build to fail

[FrelliBB]

We also started getting affected by this issue just now on our CI server, where some of our repositories were getting this dependency from jitpack, and some from maven central. This, I believe, was corrupting the .m2 repositories cache on our CI agent and causing builds to fail seemingly randomly. I don't think there's anything the maintainers of this project can do, but I want to leave this comment to help anyone who comes across a similar problem in the future.

Our fix right now is to stop using jitpack in all our repositories.

Could not find artifact com.github.java-json-tools.jackson-coreutils:jackson-coreutils:jar:2.0 in remote (https://***.jfrog.io/***/***)