Put <maven-install-dir>/conf/settings.xml on a shared drive, or replace it with a symlink to a shared drive.

Why do you need to change the settings.xml anyway? Could it not be done in a master pom that is the parent to all other poms? Then you can simply deploy the master pom and you're done.

Stefan

Matthew Tordoff wrote:
Hi all,

I just wondered if anyone has any best practises for updating the global 
settings.xml in Maven. I have considered checking the conf folder into SVN, or 
even potentially checking the whole maven install into SVN, then when changes 
are made send out an email and people can just do an SVN update to pick up the 
changes. The only disadvantage of this process is that it relies on people 
reading their mail and kicking off the update. I would preferably like a method 
of automatically publishing changes which would automatically update all 
developers machines.

Any thoughts around this would be greatly appreciated.

Regards,

Matt

P.S. I would also be interested on your views regarding checking in solely the 
settings.xml file into version control, vs checking in the whole install.

_________________________________________________________________
Free games, great prizes - get gaming at Gamesbox. http://www.searchgamesbox.com

--
best regards,

Stefan Seidel
software developer
________________________
VUB Printmedia GmbH
Chopinstraße 4
D-04103 Leipzig
Germany
tel.    +49 (341) 9 60 50 07
fax.    +49 (341) 9 60 50 92
mail.   [EMAIL PROTECTED]
web.    www.vub.de

HRB Köln 24015
UStID DE 122 649 251
GF Dr. Achim Preuss Neudorf,
Dr. Christian Preuss Neudorf

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to