[
https://issues.apache.org/jira/browse/MRESOLVER-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17750309#comment-17750309
]
ASF GitHub Bot commented on MRESOLVER-387:
------------------------------------------
grgrzybek commented on PR #319:
URL: https://github.com/apache/maven-resolver/pull/319#issuecomment-1662201804
In Camel we use custom DI registry based on Camel's
`org.apache.camel.support.SupplierRegistry`.
Here's the interface -> implementation configuration:
https://github.com/apache/camel/blob/camel-4.0.0-RC2/tooling/camel-tooling-maven/src/main/java/org/apache/camel/tooling/maven/MavenDownloaderImpl.java#L591
Roughly I checked if Camel (or
`org.eclipse.aether.supplier.RepositorySystemSupplier` in this PR, which is
impossible of course ;)) misses something
Camel misses "beans" related to these methods:
```
getArtifactResolverPostProcessors
getModelCacheFactory
getProvidedChecksumsSources
getRemoteRepositoryFilterSources
getTrustedChecksumsSources
```
but that's because Camel still uses Maven 3.8 (which will change in
https://issues.apache.org/jira/browse/CAMEL-19637) - so thanks for great
"checklist".
For example I found great
`org.eclipse.aether.spi.resolution.ArtifactResolverPostProcessor` I wasn't
aware of - there's a lot of potential in it!
> Provide "static" supplier for RepositorySystem
> ----------------------------------------------
>
> Key: MRESOLVER-387
> URL: https://issues.apache.org/jira/browse/MRESOLVER-387
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.15
>
>
> To provide SL replacement.
> Something like this
> https://github.com/maveniverse/mima/blob/main/runtime/standalone-static/src/main/java/eu/maveniverse/maven/mima/runtime/standalonestatic/RepositorySystemSupplier.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
