[
https://issues.apache.org/jira/browse/MNG-7046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777763#comment-17777763
]
Guillaume Nodet commented on MNG-7046:
--------------------------------------
If you're using the resolver, or if you programmatically build a model and ask
to resolve it, I don't think we should put any restriction here. Not sure to
understand what use case you have in mind.
> Revert MNG-5639 and make repo config static only (no ${param} interpolation)
> ----------------------------------------------------------------------------
>
> Key: MNG-7046
> URL: https://issues.apache.org/jira/browse/MNG-7046
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories, Dependencies
> Affects Versions: 3.6.3
> Reporter: Michael Osipov
> Priority: Major
>
> As discussed in MNG-5639 repositories should always be known upfront, they
> have to be static to avoid chicken and egg situations, a project should not
> influence settings. It should be the way around.
> In subsequent ticket it will be verified that repo configuration does not
> contain any expression:
> https://github.com/apache/maven/commit/d411c3fa98832e7d86d901fe86ff63ba907cf868#commitcomment-44782281.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
