[
https://issues.apache.org/jira/browse/MRESOLVER-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884373#comment-17884373
]
ASF GitHub Bot commented on MRESOLVER-397:
------------------------------------------
cstamas commented on PR #328:
URL: https://github.com/apache/maven-resolver/pull/328#issuecomment-2371857312
Given you use Guice already,
[Sisu](https://repo.maven.apache.org/maven2/org/eclipse/sisu/org.eclipse.sisu.inject/0.9.0.M3/)
is "just" +300KB (if using no_asm and you provide ASM), or +500KB extra
dependency. If you can live with that, I'd say "go with Sisu".
@basil can you point me at some building instructions where I can test some
ideas for migration?
> Deprecate Guice modules
> -----------------------
>
> Key: MRESOLVER-397
> URL: https://issues.apache.org/jira/browse/MRESOLVER-397
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Minor
> Fix For: 1.9.16
>
>
> So far resolver supported instantiation via:
> * sisu components (JSR330) -- as used in Maven
> * Guice module
> * ServiceLocator
> We should drop all non-major ones (guice, sl), as we provided replacement in
> for of resolver provider module, so we provide:
> * sisu components (JSR330)
> * maven-resolver-provider MRESOLVER-387
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
