The better Maven Central

Emanuel Moecklin
Nerd For Tech
Published in
2 min readOct 12, 2021

Maven Central is the most used repository for Java artifacts. Almost every Gradle file starts with:

buildscript {
repositories {
// maybe other repos here

Yet publishing with Sontatype, OSSHR and Nexus (this article explains the terms really well) is a very slow and painful process:


You could argue that Jfrog is biased but I fully agree with all the statements above. Now that the Jfrog alternative JCenter is gone, there’s imo only one solution left for open source projects and that solution is amazing:

Amazing because there’s literally no effort to publish artifacts once the maven or maven-publish plugin have been configured (which needs to be done in any case) -> see my other article here.

If you have a GitHub account there’s almost nothing to do to get going. Just grant access to your public repos and you’re done. And with done I mean literally done. is so simple that I didn’t even notice that my artifacts e.g. for this repo: were automatically published (while I worked on the Maven Central publication). Jitpack automatically built and published my library:

  • because it has access to my repos
  • because I tagged my commits with a version number, e.g. v1.7.3
  • because the maven-publish task was configured
  • because is an awesome tool ;-)

To use the published artifacts you need to add as a Maven repo but that’s the only tiny drawback compared to artifacts published in Maven Central:

allprojects {
repositories {
maven { url '' }

I don’t need to go through Sonatype’s painful signup process and I don’t need to set up a build pipeline in the open source repository of my choice.

I did this for Android projects (e.g. here and here) and backend Java projects (e.g. here), it’s equally simple.