md1.sonatype.com

How to Publish Artifacts to Central

You can deploy snapshots, stage releases, and promote your releases so they will be synced to The Central Repository. All you need to do is to sign up with a Sonatype JIRA account, create a JIRA ticket and make some POM/settings configuration. Read our step-by-step guide for the details.

Sonatype OSSRH (OSS Repository Hosting Service) uses Nexus to provide Maven repository hosting service for open source projects: https://oss.sonatype.org.

Why Publish to Central?

When your project's artifacts are in Central, developers using Maven, Gradle, Ivy, or any other build tool configured to download artifacts from Central have the software they need immediately available.

The alternative is to push the responsibilty for finding, assembling, and tracking your software to your end-users. While this may have been a possibility years ago, developers have grown so accustomed to quickly adding dependencies from Central that the absence of a particular is often enough to make people look elsewhere.

Publish your artifacts to Central, lower the barrier to entry for users, and you'll attract a larger community of users.


Who Publishes to Central?

The following is a partial list of the communities and projects that have adopted the http://oss.sonatype.org

  • Agimatec
  • Apache Software Foundation
  • AppFuse
  • Bitbucket
  • Boxspring
  • Cementframework
  • Codehaus
  • Codiform
  • cometd
  • Dishevelled
  • Dojo
  • Fortysix
  • Freehep
  • Github
  • Google
  • Googlecode
  • Graniteds
  • Icroco
  • Impalaframework
  • Incalk
  • Jakubholy
  • Java.net
  • Javaforge
  • Jayway
  • JBoss
  • Jeffmaury
  • Jetty
  • Joda
  • Kantega
  • Kenai
  • MTVi
  • Ontopia
  • OpenID4Java
  • OpenStreetMap
  • Opensymphony
  • OpenXRI
  • Ops4j
  • Osgi
  • Papoose
  • Plexus
  • Postgis
  • Python
  • Qi4j
  • Signpost
  • Sourceforge
  • Springme
  • SpringSource
  • Swinglabs
  • Vaadin
  • Xajile
  • ...and many, many more.