Anders Hammar wrote: > You need Maven 3.0 to be able to activate profiles in the pom by > properties set in a profile in settings.xml.
The point is that this functionality is superfluous. If you want a profile be activated based on properties in settings.xml, you may as well simply add it there to your activeProfiles section. Works also for M2. - Jörg > > /Anders > > On Wed, Oct 27, 2010 at 01:44, Jörg Schaible <[email protected]> > wrote: > >> Jon Paynter wrote: >> >> > On Tue, Oct 26, 2010 at 4:12 PM, Jörg Schaible >> > <[email protected]>wrote: >> > >> >> Hi Jon, >> >> >> >> >> >> > what am I missing here? >> >> >> >> It does simply not work this way. You cannot activate a profile by a >> >> property defined in the current or parent POM. Profiles are resolved >> >> first to build the final POM in use. See help:effective-pom. >> >> >> >> - Jörg >> >> >> >> Well that explains the source of my confusion. I'll just find another >> >> way >> > to accomplish the same thing. >> >> You can set system properties calling Maven or define properties in your >> settings.xml (IIRC). Those are respected for the profile activation. >> >> >> >> --------------------------------------------------------------------- >> 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]
