Hello, You're right - I've had this issue before too. IMO, the order of loading is this (higher numbers override lower)
1. System and command-line properties 2. Local pom.xml 3. Global settings.xml I guess the issue is that system and command-line properties cannot be distinguished at the moment, and it is desirable to have explicitly set pom properties override system ones. Yours, David > -----Original Message----- > From: Clifton [mailto:[EMAIL PROTECTED] > Sent: 16 May 2008 15:12 > To: users@maven.apache.org > Subject: Priorities of properties > > > AM I confused or does Maven override command line properties > with profile > properties in the pom and profiles.xml? Shouldn't command > line properties > always take precedence? Could somebody explain the priority order of > properties in Maven? I've been trying to do things like have > a switch in one > profile activate another but this doesn't seem to work well. > I've also run > into issues where profiles.xml properties collide with or > shadow pom.xml > properties. Is there an in depth explanation of how all this > is supposed to > work? > -- > View this message in context: > http://www.nabble.com/Priorities-of-properties-tp17274343p1727 4343.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
