[
https://issues.apache.org/jira/browse/MNG-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631598#comment-17631598
]
ASF GitHub Bot commented on MNG-7590:
-------------------------------------
michael-o commented on PR #863:
URL: https://github.com/apache/maven/pull/863#issuecomment-1310138531
> Well, sorry for late as I missed: due
https://issues.apache.org/jira/browse/MRESOLVER-284 this is not true for ANY
settings.... as we talk here only about session config properties, but if you
look at linked issue, some of config properties are expected from
PlexusContext/SisuParameters.... this also means that this PR makes it
impossible to have these expected as parameters to be set from settings.xml,
and this is why I think is better thing to do:
>
> * on short term, to have all these in `$MAVEN_ARGS` or
`.mvn/maven.conf` (or mavenrc)
>
> * on long term we need something dedicated I guess
>
>
> So, again, sorry, but I'd -1 this and rollback the commit as well, but am
open to discussion.
I don't understand the contradiction. ARen't the settings props read before
the session is created? So for those which it can apply it will apply?
> Allow configure resolver by properties in settings.xml
> ------------------------------------------------------
>
> Key: MNG-7590
> URL: https://issues.apache.org/jira/browse/MNG-7590
> Project: Maven
> Issue Type: Improvement
> Reporter: Slawomir Jaranowski
> Assignee: Slawomir Jaranowski
> Priority: Major
> Fix For: 3.9.0, 4.0.x-candidate, 4.0.0-alpha-3
>
>
> New Artifact Resolver has many useful configuration options, currently we
> only have the option to pass them as system or user properties.
> It will be useful to have possibility to provide them by properties in
> settings.xml to have whole configuration in one place.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
