Note that the server identifier listed in Listing deployment credentials in Maven Settings should match the serverId parameter you are passing to the Nexus Staging Maven plugin and in the example contains the default password for the deployment user - "deployment123". To add these credentials, add the following element to the servers element in your ~/.m2/settings.xml file as shown below: These credentials are stored in the Maven Settings file in ~/.m2/settings.xml.
#Deployit maven plugin update#
To successfully deploy to your repository manager, you will need to update your Maven Settings with the credentials for the deployment user. If no profile is found, the upload will fail. If an appropriate staging profile is found, a staging repository is created on the fly and the components are deployed into it. It will try to determine the appropriate staging profile by matching the component path with any repository targets configured with staging profiles with an activated implicit profile selection strategy. With this configuration the Nexus Staging Maven plugin will stage the components locally and connect to the repository manager. The base URL at which the repository manager to be used for staging is available. The id of the server element in settings.xml from which the user credentials for accessing the repository manager should be retrieved. The minimal required configuration parameters for the Nexus Staging Maven plugin are: This configuration works only in Maven 3 and automatically replaces the deploy goal invocation of the Maven Deploy plugin in the deploy Maven life cycle phase with the deploy goal invocation of the Nexus staging Maven plugin. Try to use the newest possible plugin version to take advantage of any available improvements.įollowing Maven best practices, the version should be pulled out into a pluginManagement section in a company POM or parent POM. The latest version of the plugin available is always compatible with the latest available version of Nexus Repository Manager Pro.
#Deployit maven plugin pro#
1.5 and 1.6.x can be used for Nexus Repository Manager Pro 2.7 to 2.10. Version 1.2 is compatible with Nexus Repository Manager Pro 2.3, Version 1.4.4 is compatible with Nexus Repository Manager Pro 2.4, Version 1.4.8 is compatible with Nexus Repository Manager Pro 2.5 and 2.6.
It is important to use a version of the plugin that is compatible with your Nexus Repository Manager Pro server. The simplest usage can be configured by adding it to the project build plugins section as an extension: The Nexus Staging Maven plugin is a specific and more powerful replacement for the Maven Deploy plugin with a number of features specifically geared towards usage with the staging suite. Deployment with the Nexus Staging Maven Plugin
#Deployit maven plugin manual#
With all tools you can use the manual upload of your components documented in Manually Uploading a Staged Deployment. If you need to continue to use the Maven Deploy plugin, you can read about using it with the staging suite in Deployment with the Maven Deploy Plugin. The preferred way to do this is to take advantage of the features provided by the Nexus Staging Maven plugin or the Nexus Staging Ant tasks as documented in Deployment with the Nexus Staging Maven Plugin and Deployment with the Nexus Staging Ant Tasks.
Once the repository manager is configured to receive components in the staging suite as documented in Configuring the Staging Suite, you will have to update your project build configuration to deploy to the staging suite.
0 kommentar(er)
