[
https://issues.apache.org/jira/browse/MNG-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17699284#comment-17699284
]
Tamas Cservenak commented on MNG-7726:
--------------------------------------
With PR as expected:
{noformat}
<profiles>
<profile>
<id>example1</id>
<activation>
<file>
<exists>/home/cstamas/tmp/MNG-7726/test.txt</exists>
</file>
</activation>
</profile>
<profile>
<id>example2</id>
<activation>
<file>
<exists>/home/cstamas/tmp/MNG-7726/test2.txt</exists>
</file>
</activation>
</profile>
{noformat}
> Maven 3.9.0 resolves properties in file profile activation incorrectly
> ----------------------------------------------------------------------
>
> Key: MNG-7726
> URL: https://issues.apache.org/jira/browse/MNG-7726
> Project: Maven
> Issue Type: Bug
> Components: Profiles
> Affects Versions: 3.9.0
> Reporter: Kalle Lindqvist
> Assignee: Tamas Cservenak
> Priority: Minor
> Fix For: 3.9.1
>
> Attachments: example2.file.path=test2.txt, pom.xml, test.txt
>
>
> With the provided files when you run:
> {code:java}
> mvn help:active-profiles{code}
> The profile example1 should be activated and that is the case if you use
> maven version 3.8.7 or 4.0.0-alpha4. But in version 3.9.0 instead the profile
> example2 is activated, for some reason ${example2.file.path} is resolved as
> "example2.file.path=test2.txt" instead of "test2.txt".
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
