Page History

...

Thus artifacts can be safely deployed to Nexus as part of voting on a release. The vote takes place on the staged artifacts. If the vote succeeds, the artifacts can be promoted to the live repository. If it fails, the artifacts can be deleted, and the process can restart.

It also allows redundant files (such as .asc.md5 and .asc.sha1 hashes) to be deleted before deployment.

Preparations for using Nexus

• All Commons projects components that use the org.apache.commons groupId are already set up to use Nexus.

However,

...

components that use different groupIds may need to be set up.

...

Just create a JIRA subtask under https://issues.apache.org/jira/browse/INFRA-1896, for example see: https://issues.apache.org/jira/browse/INFRA-2725 (Commons) or https://issues.apache.org/jira/browse/INFRA-2799 (CLI)

...

As noted above, there are two different repositories, one for snapshots and the other for releases. If the version contains the suffix -SNAPSHOT, then the snapshot repo will be chosen by mvn deploy otherwise it deploy will use the release repo.

...

To create the snapshot, make sure that the current directory pom.xml is for a SNAPSHOT version. Perform the following command:

...

Creating a Nexus staging release

...

Make sure you are using Commons Parent V16 or later.

This is necessary to ensure that Nexus is used as the deployment target.

...