Sounds reasonable to me, and should be easy enough to test that it works etc before committing everyone to it, only to discover a problem, etc.
Wayne On 7/31/07, Baz <[EMAIL PROTECTED]> wrote: > Dana, Wayne, > > What about this? > > 1. Change mvn.bat to do "-s $MVN_SETTING_FILE". > 2. Define MVN_SETTING_FILE in the shell environment. > 3. Point the MVN_SETTING_FILE to the default workspace location where your > SCM tool will update the latest settings.xml (or any name in this case) > > This way, you can use default and customize if you want by changing the > environment variable. This seems like a flexible solution. Comments? > > > > On 7/31/07, Lacoste, Dana <[EMAIL PROTECTED]> wrote: > > > > We checked into our project home a "settings.xml.sample" so that users > > could customize their own environment. > > > > But if you added the "-s" flag to your maven command in cruise control > > you could force it to use the checked in/perforce version at build time > > (then just get the developers to use the shared one as well) > > > > Dana > > > > -----Original Message----- > > From: Baz [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, July 31, 2007 12:20 PM > > To: Maven Users List > > Subject: setting default location of settings.xml > > > > Hi, > > > > Is there a way to setup default location of settings.xml? I understand > > the default location is M2 repo. > > > > I am trying to have settings.xml stored in Perforce and add an > > environment variable to point to a directory so developers can have a > > consistent settings.xml file. Suggestion? > > > > Thanks. > > > > A. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
