[
https://issues.apache.org/jira/browse/MRESOLVER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898203#comment-17898203
]
ASF GitHub Bot commented on MRESOLVER-628:
------------------------------------------
cstamas opened a new pull request, #601:
URL: https://github.com/apache/maven-resolver/pull/601
As original solution using map.hashCode may clash, and in that case runtime
"just in time" class clast issue happens.
Rather provide explicit discriminator class "what is in maps" and use that
to create key to cache in session.
---
https://issues.apache.org/jira/browse/MRESOLVER-628
> Class cast issue (probably concurrency issue)
> ---------------------------------------------
>
> Key: MRESOLVER-628
> URL: https://issues.apache.org/jira/browse/MRESOLVER-628
> Project: Maven Resolver
> Issue Type: Bug
> Components: Resolver
> Affects Versions: 2.0.0, 2.0.1, 2.0.2, 2.0.3
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 2.0.4
>
>
> Errors may happen like:
> {noformat}
> Caused by: java.lang.ClassCastException: class
> org.eclipse.aether.transport.jdk.JdkTransporterFactory cannot be cast to
> class org.eclipse.aether.spi.connector.RepositoryConnectorFactory
> (org.eclipse.aether.transport.jdk.JdkTransporterFactory and
> org.eclipse.aether.spi.connector.RepositoryConnectorFactory are in unnamed
> module of loader org.codehaus.plexus.classworlds.realm.ClassRealm @548c4f57)
> {noformat}
> Probably cause: prioritized component caching in session
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
