[
https://issues.apache.org/jira/browse/MNG-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17839466#comment-17839466
]
ASF GitHub Bot commented on MNG-8081:
-------------------------------------
mbenson commented on PR #1477:
URL: https://github.com/apache/maven/pull/1477#issuecomment-2068442626
I notice that this implementation _only_ interpolates properties in property
activations, whereas my submitted implementations for both v3.9.x and v4
attempt to satisfy the "least surprise" principle by applying interpolations to
_all_ property activations. IMHO that's the best way forward but I am satisfied
if this PR becomes the 3.9.x implementation.
> default profile activation should consider available system and user
> properties
> -------------------------------------------------------------------------------
>
> Key: MNG-8081
> URL: https://issues.apache.org/jira/browse/MNG-8081
> Project: Maven
> Issue Type: Improvement
> Components: Profiles
> Affects Versions: 3.9.6, 4.0.0
> Reporter: Matthew Jason Benson
> Priority: Minor
> Fix For: 3.9.7, 4.0.0, 4.0.0-alpha-14
>
>
> As discussed in my open PR, my use case is to compare between environment
> variables e.g.:
> {code:java}
> <activation>
> <property>
> <name>env.FOO</name>
> <value>${env.BAR}</value>
> </property>
> </activation>{code}
> Limiting the interpolation to user/system properties means that there is no
> mindf*ck resulting from profile activation order, etc., and keeps this
> request nonthreatening.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
