[ 
https://issues.apache.org/jira/browse/MNG-8081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841329#comment-17841329
 ] 

ASF GitHub Bot commented on MNG-8081:
-------------------------------------

gnodet commented on PR #1446:
URL: https://github.com/apache/maven/pull/1446#issuecomment-2079833746

   > hi @gnodet ... so with the implementation having been largely duplicated 
from model-builder into api-impl, would the similar code remain in both places 
indefinitely, or will the model-builder code eventually point directly to 
api-impl?
   
   The code in model-builder should be deprecated, it will be kept for 
compatibility with 3.x plugins for some time, and then removed.  Not sure about 
the exact dates though.  The point is that model-builder is not really used 
anymore in beta-1.




> 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
>            Assignee: Guillaume Nodet
>            Priority: Minor
>             Fix For: 3.9.7, 4.0.0, 4.0.0-beta-1
>
>
> 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)

Reply via email to