maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anders Hammar <>
Subject Re: Can't specify distributionManagement in settings.xml
Date Tue, 05 Oct 2010 06:29:23 GMT
Have a look at this parent:

There you see that properties are used for both the repo name and url. This
makes it possible to override these values from command line. This is
normally not anything you do, but it's very handy when you want to e.g.:
* deploy somewhere else (like to a test repo when you're doing some
experiments and want to use some test repo)
* want to use some other repo id for your cred matching in settings.xml
(maybe you have the same credentials everywhere, but instead of having 10-20
server elements you just want to use one single)

Regarding staging: If you're serious about your Maven implementation I would
recommend having a look at the staging support of Nexus Pro. Sure, it's not
free but it is superior to the stage plugin and gives you the possibility to
also add automated checks. As Apache and Codehaus now uses Nexus Pro, I
would guess that nobody is working on the stage plugin any more. Which kind
of makes you on your own should you run into any issues. Well, just my


On Tue, Oct 5, 2010 at 06:45, Phillip Hellewell <> wrote:

> On Mon, Oct 4, 2010 at 2:58 PM, Ron Wheeler
> <> wrote:
> >  On 04/10/2010 4:28 PM, Phillip Hellewell wrote:
> >>
> >> Yeah, part of the problem is I still haven't got this working with a
> >> "parent" pom, and I don't even know exactly what is meant by a parent
> >> pom (I assume it was using the<parent>  tag, but I'm running into
> >> issues there...)
> >>
> > ??? Should not be any there.
> Just tried using a parent pom tonight and it worked fine.  Not sure
> what was going on earlier today.
> I'm still not fully convinced of the necessity of persisting an
> artifact's default deploy location, but I'm going to take your guys'
> word for it and do it the "Maven way".  And I'll try to do whatever I
> can with DNS or virtual hosts or whatever to make it so that doesn't
> have to change unnecessarily.
> BTW, I'm thinking that we will probably have two main repositories, a
> "staging" one and a "release" one.  Any build that succeeds and unit
> tests pass will be deployed automatically to the staging repo (which
> will be the default repo referenced by all the poms, well, the parent
> pom).  Then after QA approval it will be deployed to the "release"
> repo.  But if -DaltDeploymentRepository is buggy, maybe I should put a
> variable in there.  Or can I just use the stage plugin to copy an
> artifact from the staging to release repo?
> Phillip
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message