[
http://jira.codehaus.org/browse/MNG-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118759
]
Richard van der Hoff commented on MNG-2276:
-------------------------------------------
See MNG-2848 for activating profiles via env vars.
Activating profiles via properties defined in other profiles (as would be the
case for defining a property in settings.xml) is a whole, more complicated,
kettle of fish; i guess mvn 2.1 might look at this sort of thing...
> profile activation by property doesn't work with properties defined in
> settings.
> --------------------------------------------------------------------------------
>
> Key: MNG-2276
> URL: http://jira.codehaus.org/browse/MNG-2276
> Project: Maven 2
> Issue Type: Bug
> Components: POM
> Affects Versions: 2.0.4
> Reporter: Brian Fox
> Fix For: 2.1
>
>
> Activating a profile like below doesn't get activated unless the property is
> set on the CLI. I need to have the property defined in the settings.xml so
> it's always set.
> <profiles>
> <profile>
> <id>prod</id>
> <activation>
> <property>
> <name>deploy-ct</name>
> </property>
> </activation>
> Further, I noticed that if I set it so that the activation is like:
> <activation>
> <property>
> <name>deploy-ct</name><value>true</value>
> </property>
> </activation>
> The profile is triggered just by setting the cli like "mvn -Ddeploy-ct" It
> is not active if I use "-Ddeploy-ct=false" but the settings descriptor says
> that the existence of the property is only used if value is not set.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
