[
https://issues.apache.org/jira/browse/MRESOLVER-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884381#comment-17884381
]
ASF GitHub Bot commented on MRESOLVER-397:
------------------------------------------
basil commented on PR #328:
URL: https://github.com/apache/maven-resolver/pull/328#issuecomment-2371874963
@cstamas This is a test framework, so the added Sisu dependency would be
fine for us. Thanks for confirming that Sisu is the preferred migration path
for heavy Guice users. As far as building instructions,
https://github.com/jenkinsci/acceptance-test-harness/blob/master/docs/DOCKER.md
is the best place to start. For testing Guice integration, you could probably
even avoid Docker and simply use e.g. `run.sh firefox latest
-Dtest=plugins.AntPluginTest#autoInstallAnt`.
> 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)
