A producer is an entity that would like publish content into the Central repository.
Whether you are an individual running a small open source project, a group of developers with a few projects or a large organization running your own repository manager publishing open source components - we can help you with publishing them to the Central Repository and provides the benefits of the Central Repository to your users.
Once released/published, you will not be able to remove/update/modify that artifact
We provide the option to publish artifacts using the
-SNAPSHOT suffix in
case that you need to do any test on your publishing process, but once
it is released there is no possibility to change it. Please check the
Can I change, modify, delete, remove, or update a component on Central?
FAQ for more details.
Individual Projects - Open Source Software Repository Hosting (OSSRH)⚓︎
Sonatype's Open Source Software Repository Hosting (OSSRH) service is the primary avenue for project owners and contributors to publish their components to the Central Repository. It is a hosted deployment of Nexus Repository Manager with the Nexus Staging Suite used for the deployment process and validation, combined with a sync process to the Central Repository content delivery network.
To use OSSRH you need to follow a few simple steps for initial setup. Before you proceed, there are a few items to consider with regard to our validation process:
As stated in our article, choosing your coordinates, you must choose a groupId for a Web Domain that you own, or for which you are the designated maintainer on behalf of the owner. We also support personal sites.
- In the case of Github, Gitee, Bitbucket or similar groupIds
(io.github.username), you must create a temporary, public repository named
OSSRH-TICKETNUMBER. Check the details in the Coordinates document.
- For all other owned domains, be prepared to verify domain ownership creating a TXT record in your Domain Register Service referencing your OSSRH ticket number.
Once you've considered the above, proceed to the following steps:
After that, you can publish as many components and releases under the provided Group ID and any nested Group ID values to the Central Repository as often as you like.
For detailed publishing instructions, please follow our step-by-step guide.