[
https://issues.apache.org/jira/browse/MRESOLVER-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750643#comment-17750643
]
Tamas Cservenak edited comment on MRESOLVER-394 at 8/3/23 8:54 AM:
-------------------------------------------------------------------
Am thinking loud here....
* the new maven-resolver-supplier module is NOT and WILL NOT be present in
Maven as it does not use it, it uses Sisu DI
* hence, if session supplier is added to it, and we deprecate
MavenRepositorySystemUtils, how will Maven irtself create session?
* for maven-resolver-supplier users, maven-resolver-provider is already (and
has to be) on classpath, so they can use it (is needed to make resolver
complete)
Ideas or remarks?
Unless there is some very good reason (and idea where to put it), am getting to
opinion to -1 on this due reasons above.
was (Author: cstamas):
Am thinking loud here....
* the new maven-resolver-supplier module is NOT and WILL NOT be present in
Maven as it does not use it, it uses Sisu DI
* hence, if session supplier is added to it, and we deprecate
MavenRepositorySystemUtils, how will Maven irtself create session?
* for maven-resolver-supplier users, maven-resolver-provider is already (and
has to be) on classpath, so they can use it (is needed to make resolver
complete)
Ideas or remarks?
> Provide "static" supplier for RepositorySystemSession
> -----------------------------------------------------
>
> Key: MRESOLVER-394
> URL: https://issues.apache.org/jira/browse/MRESOLVER-394
> Project: Maven Resolver
> Issue Type: Improvement
> Components: Resolver
> Reporter: Grzegorz Grzybek
> Priority: Major
> Fix For: 1.9.15
>
>
> Similar to MRESOLVER-387, but for DefaultRepositorySystemSession, so we can
> also deprecate
> {{org.apache.maven.repository.internal.MavenRepositorySystemUtils.newSession()}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
