[
http://jira.codehaus.org/browse/MNG-4471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MNG-4471:
-----------------------------------
Attachment: pom.xml
I slightly modified your test POM to allow for better testing. Running
{noformat}
mvn org.apache.maven.plugins:maven-help-plugin:2.1:effective-pom -V
{noformat}
on this POM I get
{noformat}
...
<properties>
<profile>ACTIVATED</profile>
<test>M:\am\3.0-alpha-5\bin\..</test>
</properties>
</project>
...
{noformat}
in the console output, i.e. I failed to reproduce the issue.
If you receive an effective POM using the above command where the property
{{test}} is present but {{profile}} not, please attach this log and re-open the
issue. In this case, it would also be nice to know whether Maven 2.x behaves
differently.
Otherwise, I assume the environment variable is simply not properly set on your
machine, i.e. {{export M2_HOME=...}}.
> Profile activation fails if <file> contains variables
> ------------------------------------------------------
>
> Key: MNG-4471
> URL: http://jira.codehaus.org/browse/MNG-4471
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 3.0-alpha-5
> Environment: Mac OS X 10.6.2
> Reporter: J C
> Attachments: pom.xml, testcase.xml
>
>
> See the attached testcase.
> The profile is not activated when <file> has variables in it:
> <file><exists>${env.M2_HOME}/bin/mvn</exists></file>
> But when the path is absolute, it works:
> <file><exists>/my/maven/home/bin/mvn</exists></file>
--
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
