On Mon, Oct 4, 2010 at 2:58 PM, Ron Wheeler <rwhee...@artifact-software.com> 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
