[ https://issues.apache.org/jira/browse/MNG-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17836674#comment-17836674 ]
ASF GitHub Bot commented on MNG-8081: ------------------------------------- mbenson commented on PR #1446: URL: https://github.com/apache/maven/pull/1446#issuecomment-2052059016 @gnodet do you have any thoughts on the best way to backport this feature to Maven 3? https://github.com/apache/maven/pull/1447 is my original PR, but a wildly divergent implementation may cause headaches in future. I wonder if it would make sense [from a future merge perspective] to stabilize the v3 impl and include the same commit in this branch prior to being replaced by the actual v4 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)