I've been following these threads and I think you're going way outside of what should be needed. You originally wanted to define a group and version as a property, presumably because you want to centrally control it rather than it would actually change it.
The proper way to control the version is via a dependencyManagement section in a parent pom that is centrally controlled (and shared by all your projects). You could also define the properties in a parent pom as well. You do have the option of defining profiles in the pom.xml (again most likely from a commonly inherited one) or with the profiles.xml, but I don't think this is what you really need. --Brian -----Original Message----- From: Thomas Chang [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 02, 2008 10:26 AM To: Maven Users List Subject: Re: How to configure the location of "settings.xml"? Your answer sounds good. But could the "profile.xml" be called? Have you an example? ****************** It sounds like you should probably be using a profiles.xml file in your project root directory (same dir as pom.xml), rather than configuring a new location for your settings.xml file etc. Wayne On 1/2/08, Erez Nahir <[EMAIL PROTECTED]> wrote: > you can use mvn -s < Alternate path for the user settings file > > > Erez. > > On Jan 2, 2008 5:05 PM, Thomas Chang <[EMAIL PROTECTED]> wrote: > > > Hi all, > > > > Normally the "settings.xml" is located under /m2_home/conf. Is it > > possible to move this file anywhere for example /myproject/conf? If yes, > > how? > > > > Regards > > > > Thomas > > > > > > --------------------------------- > > Heute schon einen Blick in die Zukunft von E-Mails wagen? Versuchen Sie´s > > mit dem neuen Yahoo! Mail. > > --------------------------------- Ihr erstes Baby? Holen Sie sich Tipps von anderen Eltern. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
