maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "alex.price" <>
Subject Nexus Staging Maven Plug-in
Date Wed, 27 Feb 2013 16:57:20 GMT

I am currently implementing the "Nexus Staging Maven Plug-in" for many of
our releases, which aims to place artifacts in the Nexus Staging area in an
automated "closed" state.

I am currently reading the Sonatype article on the plug-in:

I have noticed a paragraph in this article which concerns me slighly, and
wanted clarification on what the statement means:

/"The implicit matching relies on the setup of repository targets as well as
the correct order of staging profiles and is therefore an error prone
approach when many staging profiles are in use.

The preferred way to work in this sceneario is to change the profile
selection strategy on all staging profiles to explicit only and pass the
staging profile id to the Nexus Staging Maven Plugin using the
stagingProfileId configuration parameter as documented above."/

What number of Staging profiles would this be talking about? Would this
definitely be solved if a stagingProfileId parameter was used? What other
factors could effect this "error prone approach"?



View this message in context:
Sent from the Maven Developers mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message