[jira] [Comment Edited] (MRESOLVER-157) Get rid of ServiceLocator in Resolver

["Václav Haisman (Jira)" <ji...@apache.org>]

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

Václav Haisman edited comment on MRESOLVER-157 at 9/30/22 11:21 AM:
--------------------------------------------------------------------

We are using Maven Resolver in Spring Boot application. How would we instantiate Maven Resolver without SL in such environment? 


was (Author: wilx):
We are using Maven Resolver in Spring Boot application. How would be we instantiate Maven Resolver without SL in such environment? 

> Get rid of ServiceLocator in Resolver
> -------------------------------------
>
>                 Key: MRESOLVER-157
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-157
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Tamás Cservenák
>            Priority: Major
>
> maven-resolver currently supports:
>  * ServiceLocator (deprecated as of 1.7.0 see MRESOLVER-160)
>  * "vanilla" Guice (provides a module)
>  * DI using Sisu, as used in Maven
> IMO, it makes not much sense to support 3 vastly different "DI"s (in quotes as ServiceLocator is really just a dumb factory pattern).
> Not only just complicates the code base, makes changes error prone at least, yields for "exceptions" (this or that will never work with it, as seen with SyncContext), and, for me most importantly, prevents proper constructor initialization and validation of components.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)