maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manfred Moser" <>
Subject Re: Nexus Staging Maven Plug-in
Date Thu, 28 Feb 2013 18:43:02 GMT
Hi Alex,

I wrote that advice. The reasons is that depending on your package
structure and number of different team needing different staging profiles
I can become hard to maintain all the repository targets and profiles
matching correctly. We have certainly found that to be the case with OSSRH
where there are hundreds of profiles. However it can also be brittle in
smaller setups with dozens of profiles where deployments can then end up
in wrong staging repositories.

Using the explicit matching is definitely the way to go since it is less
work and less error prone.  And it works against the central repo as well.
E.g. look for an example config here

 > Hi,
> 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"?
> Thanks,
> Alex.
> --
> View this message in context:
> Sent from the Maven Developers mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message