[
http://jira.codehaus.org/browse/MNG-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-2848.
---------------------------
Assignee: John Casey (was: Vincent Siveton)
Resolution: Fixed
Looks like the system-property-setting has been reinstated, and the execution
properties are still setup and used internally as specified in the patch. This
is probably the best we can expect for now, unless/until we find a way to
control the way plugins use (and more importantly, pass on to their delegates)
the system properties.
I'm closing this issue. We can open a new one later if we need to fine-tune
this behavior further.
> Environment variables in profile activation not working
> -------------------------------------------------------
>
> Key: MNG-2848
> URL: http://jira.codehaus.org/browse/MNG-2848
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 2.0.4, 2.0.5
> Environment: Windows XP Professional, JDK 1.5
> Reporter: Muhammad Alsebaey
> Assignee: John Casey
> Fix For: 2.0.9
>
> Attachments: MNG-2848.patch
>
>
> When using an environment variable as a profile activation variable, it
> doesnt work, using either env.X or ${env.X} doesnt work.
> I found the same issue on the forums unresolved.
> http://www.nabble.com/profile-activation-based-on-environment-variables-tf2585492s177.html#a7208580
> Basically, the following doesnt work, where FOO is a windows environment
> variable (like PATH for example) :
> {code:xml}
> <profile>
> <id>haroon-workstation</id>
> <activation>
> <property>
> <name>env.FOO</name>
> <value>foo</value>
> </property>
> </activation>
> .......
> </profile>
> {code}
--
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
