Hehe. It always gets back to that. Not sure why your hung up over it ;-).
What Arnaud is saying does make more sense to me. There is at least a fixed place in some POM in source control which defines the default location of where to deploy to. At least this is tracable. I am not really all that found of making it a variable though. That just sounds like extra work for very little gain. > -----Original Message----- > From: Phillip Hellewell [mailto:ssh...@gmail.com] > Sent: Monday, October 04, 2010 3:40 PM > To: Maven Users List > Subject: Re: Can't specify distributionManagement in settings.xml > > On Mon, Oct 4, 2010 at 1:36 PM, Phillip Hellewell <ssh...@gmail.com> > wrote: > > 2010/10/4 Arnaud Héritier <aherit...@gmail.com>: > >> Wrong :-) > >> Let me try to explain ... > >> Your approach to allow to override this parameter using a property is > good. > >> I'm doing it to validate a new version of my repository manager and so > on. > >> But how you are doing it is wrong. > > > > I didn't know I could define properties outside of a profile section. > > Let me give it a try... > > Crap, you can't do that in a settings.xml. To do it outside of a > profile section it has to be in a pom, so that leads me back to having > to use a parent or "corporate" pom :( > > Phillip > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org
