[
https://issues.apache.org/jira/browse/MRESOLVER-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633632#comment-17633632
]
ASF GitHub Bot commented on MRESOLVER-291:
------------------------------------------
cstamas commented on PR #219:
URL: https://github.com/apache/maven-resolver/pull/219#issuecomment-1313372158
> Currently, the Redisson or Hazelcast clients are only initiated when the
specific lock is required, even if the JARs are on the CP. Does this change to
the worse?
That's not true, this is the ctor of support class
https://github.com/apache/maven-resolver/blob/master/maven-resolver-named-locks-redisson/src/main/java/org/eclipse/aether/named/redisson/RedissonNamedLockFactorySupport.java#L53
It creates cliean in ctor, that I guess, needs to be shut down.
> Undo MRESOLVER-284
> ------------------
>
> Key: MRESOLVER-291
> URL: https://issues.apache.org/jira/browse/MRESOLVER-291
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.1
>
>
> No semantics change, merely do not expect ctor config injection, use session
> configuration params for everything as originally intended.
> The MRESOLVER-284 "breaking" part should be undone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
