Moving a project to Maven Central

Question

I manage many maven projects. Most of them are deployed in our internal maven repository. Now I would like to start the release of one project in Maven Central. Until now, I had a parent POM that indicated the distribution of control of our internal repository. It makes no sense to deploy this information to Maven Central.

How do I specify distribution management for my internal projects? Should I have a separate pom-internal parent group for internal projects?

Sonatype mentions the deployment method directly in their repositories, but they recommend using their own parent pom (oss-parent). Looking at projects using mvnrepository.org, I could not find any projects with an oss parent. Do most projects manually deploy their artifacts in Sonatype? Where and how do they deploy them first?

So many questions! I am amazed at how complicated this is ...

Update: it turns out that some of the projects that I have defined use oss-parent. It is simply hidden as the parent of the parent.

Answer 1

Once you are configured, you can deploy the phased releases and SNAPSHOTs directly to the Sonatype OSS repository. Release versions can then be released through the Sonatype Nexus interface .

To create a repository folder for your application that you can deploy, you open a ticket using Sonatype on your JIRA along with a link to the open source project that you will deploy. The process is very smooth, and Sonatype will help you if you do not provide all the necessary information.

While on the first glace it does not look like many projects have oss-parent as a parent, they often occur when navigating the POM tree. For example, Google Guava has a parent guava-parent that has a parent oss-parent . When your project has oss-parent and a repository is set up, you can easily deploy SNAPSHOT and release using mvn deploy or mvn release:prepare release:perform .

It seems overwhelming, but it's easy to understand if you just go through all the steps for the first time.

Answer 2

The first thing I recommend reading is: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide A relative of OSS does under a special circumstance under another not. It depends on which project you want to distribute.

UPDATE : this link is now dead. Look here for deployment assistance at Sonatype.

UPDATE For Maven Central check this out: http://central.sonatype.org/