[
https://issues.apache.org/jira/browse/MRESOLVER-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17884368#comment-17884368
]
ASF GitHub Bot commented on MRESOLVER-397:
------------------------------------------
basil commented on PR #328:
URL: https://github.com/apache/maven-resolver/pull/328#issuecomment-2371842156
Hi @cstamas, we are currently relying on this deprecated functionality in
the Jenkins Acceptance Test Harness (ATH), a Guice-based project that also uses
Maven Resolver to fetch Jenkins plugins for tesitng purposes. The relevant
functionality is here:
https://github.com/jenkinsci/acceptance-test-harness/blob/9b7b87da2b1d5873876d156756f8849b26fcbc16/src/main/java/org/jenkinsci/test/acceptance/utils/aether/AetherModule.java
Thank you very much for including this note:
> This class is about to be dropped in 2.0.0 release. Use
[Sisu](https://projects.eclipse.org/projects/technology.sisu) or use [Maven
Resolver
Supplier](https://maven.apache.org/resolver/third-party-integrations.html) to
get `Resolver` instances.
However, I am not sure whether Sisu or Maven Resolver Supplier would be
better for our use case. Since we are already using Guice, would Sisu be the
preferred migration path? And if so, are there any examples you could point to?
> 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)
