download artifacts from nexus repository

The production automation and deployment space has thousands of options from Puppet to ControlTier to OSGi-based solutions to approaches that involve a series of custom scripts. Deployment Scripts: What to write them in Once you've mastered complex assemblies and created Matrix jobs to publish release artifacts to Nexus, you start to see Nexus as a central part of your approach to deploying software to various environments. The deploy goal of the plugin is mapped to the deploy phase of the Maven build.Īlso notice that, as discussed, we do not need staging functionality in a simple deployment of -SNAPSHOT artifacts to Nexus, so that is fully disabled via the element.īy default, the deploy goal includes the staging workflow, which is recommended for release builds.If you've used Nexus for development and you've perfected the art of continuous integration, you may have noticed that Nexus does more than just support development. So, the first step in using another deployment plugin in the deploy phase is to disable the existing, default mapping: However, unlike other components that may actually change throughout the lifecycle of a project, the Maven Repository Manager is highly unlikely to change, so that flexibility is not required.

The only reason to use the maven-deploy-plugin is to keep open the option of using an alternative to Nexus in the future – for example, an Artifactory repository.

Because of that fact, Sonatype built a Nexus specific plugin – the nexus-staging-maven-plugin – that is actually designed to take full advantage of the more advanced functionality that Nexus has to offer – functionality such as staging.Īlthough for a simple deployment process we do not require staging functionality, we will go forward with this custom Nexus plugin since it was built with the clear purpose to talk to Nexus well. The maven-deploy-plugin is a viable option to handle the task of deploying to artifacts of a project to Nexus, but it was not built to take full advantage of what Nexus has to offer. By default, Maven handles the deployment mechanism via the maven-deploy-plugin – this mapped to the deployment phase of the default Maven lifecycle:

Download artifacts from nexus repository