Details
Bug
Description
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) :
<profile> <id>haroon-workstation</id> <activation> <property> <name>env.FOO</name> <value>foo</value> </property> </activation> ....... </profile>
Attachments
Issue Links
| This issue is related to: | ||||
| MNG-1753 | support improved property based profile activation |
|
|
|
Has there been any resolution to this issue? I am currently also trying to access environment variables from within <profile> (be it within profiles.xml and pom.xml) with no success. Outside of <profile>, I can access environment variables just fine, but within <profile>, using the environment variable as an activation property, does not seem to work.
I've been unsuccessful trying to access the variable using the following methods within <profile>:
env.FOO
FOO
${env.FOO}
${FOO}
Any information reguarding this issue would be greatly appreciated... especially since this has been an issue for well over a year now (referring to http://jira.codehaus.org/browse/MNG-2276 ).
Defining the variable via the commandline interface does work however, as stated in the link above.
Btw, my version of maven is 2.0.7