[jira] Commented: (MNG-2276) profile activation by property doesn't work with properties defined in settings.
[ http://jira.codehaus.org/browse/MNG-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=224818#action_224818 ] Mark Michaelis commented on MNG-2276: - If my evaluation is correct it also means that profiles from parent POMs cannot activate profiles in child POMs. Is this correct? 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 3 Issue Type: Bug Components: POM, Profiles Affects Versions: 2.0.4 Reporter: Brian Fox Assignee: Benjamin Bentmann Fix For: 3.0-beta-1 Attachments: mng-2276.zip 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 idprod/id activation property namedeploy-ct/name /property /activation Further, I noticed that if I set it so that the activation is like: activation property namedeploy-ct/namevaluetrue/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
[jira] Commented: (MNG-2276) profile activation by property doesn't work with properties defined in settings.
[ http://jira.codehaus.org/browse/MNG-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=139833#action_139833 ] Basil James Whitehouse III commented on MNG-2276: - Can someone with privileges please add 'Profiles' to the affected components to make it easier for others to find this issue. 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 idprod/id activation property namedeploy-ct/name /property /activation Further, I noticed that if I set it so that the activation is like: activation property namedeploy-ct/namevaluetrue/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
[jira] Commented: (MNG-2276) profile activation by property doesn't work with properties defined in settings.
[ 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 idprod/id activation property namedeploy-ct/name /property /activation Further, I noticed that if I set it so that the activation is like: activation property namedeploy-ct/namevaluetrue/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
[jira] Commented: (MNG-2276) profile activation by property doesn't work with properties defined in settings.
[
http://jira.codehaus.org/browse/MNG-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93026
]
Immo Huneke commented on MNG-2276:
--
Moreover, profile activation based on environment variables doesn't seem to
work at all. For example:
{code}
profile
activation
property
nameenv.APPSERVER_ROOT/name
/property
/activation
{code}
This is ignored, but if the name is java.vendor.url it works fine (because that
property is always defined).
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.x
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
idprod/id
activation
property
namedeploy-ct/name
/property
/activation
Further, I noticed that if I set it so that the activation is like:
activation
property
namedeploy-ct/namevaluetrue/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
