Warning: the "artifactId" of the plugin is newly introduced! The old nexus-maven-plugin is deprecated!įurther user documentation is also available in the staging chapter of the free book Repository Management with Nexus:
Hence, the nexus-staging-maven-plugin is introduced, with vastly enhanced support. Nexus Staging V2 focuses more on client-server automated interaction. DependencyĬom.google.guava : guava : 14.0.1 Documentation The identified vulnerabilities are in classes not used. The identified vulnerabilities are in classes which are not used directly or in any of the plugin dependency code. The identified vulnerabilities are in methods not used. The out-of-the-box logback configuration used is not vulnerable. The identified vulnerabilities are in classes which are not used. Sonatype investigation has determined the following are not applicable. Some vulnerabilities may be reported against this plugin by security analysis tools. Vulnerabilities Dependency Vulnerabilities Not Impacting nexus-staging-maven-plugin
While the maven plugin ("staging client") part is OSS, to use staging features it need a Sonatype Nexus Professional instance 2.1+ on the server side! | anything, you could just leave off the inside the activation-property.Maven Plugin to control Nexus Staging workflow. | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to | This profile example uses the JDK version to trigger activation, and provides a JDK-specific repo. | to accomplish, particularly when you only have a list of profile id's for debug. | This will make it more intuitive to understand what the set of introduced profiles is attempting | for profiles, such as 'env-dev', 'env-test', 'env-production', 'user-jdcasey', 'user-brett', etc. | An encouraged best practice for profile identification is to use a consistent naming convention
| or the command line, profiles have to have an ID that is unique. > release admin admin123 snapshots admin admin123