[ 
https://issues.apache.org/jira/browse/MNG-8481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17909548#comment-17909548
 ] 

Tamas Cservenak edited comment on MNG-8481 at 1/3/25 10:52 AM:
---------------------------------------------------------------

You must keep all resolver modules aligned. Maven 3.9.9 uses 1.9.22, you cannot 
"jump" to 2.x resolver bits and mix them with 1.x resolver bits.

Try 
https://repo.maven.apache.org/maven2/org/apache/maven/resolver/maven-resolver-named-locks-redisson/1.9.22/
 with Maven 3.9.9 please (or version that Maven 3.9.6 use)


was (Author: cstamas):
You must keep all resolver modules aligned. Maven 3.9.9 uses 1.9.22, you cannot 
"jump" to 2.x resolver bits and mix them with 1.x resolver bits.

> NamedLockFactory discovery stopped working on Maven 3.9.9 and Named Locks 
> 2.0.5
> -------------------------------------------------------------------------------
>
>                 Key: MNG-8481
>                 URL: https://issues.apache.org/jira/browse/MNG-8481
>             Project: Maven
>          Issue Type: Bug
>          Components: Class Loading
>    Affects Versions: 3.9.9
>            Reporter: Elias Balasis
>            Priority: Major
>
> On Maven 3.9.6 with {{maven-resolver-named-locks-redisson-1.9.18}} discovery 
> of the {{NamedLockFactory}} works.
> However, on Maven 3.9.9 with maven-resolver-named-locks-redisson-2.0.5 the 
> following error is produced:
> {code}
> [ERROR] Internal error: java.lang.IllegalArgumentException: Unknown 
> NamedLockFactory name: 'rwlock-redisson', known ones: [file-lock, 
> rwlock-local, semaphore-local, noop] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: 
> java.lang.IllegalArgumentException: Unknown NamedLockFactory name: 
> 'rwlock-redisson', known ones: [file-lock, rwlock-local, semaphore-local, 
> noop]
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:109)
>         at org.apache.maven.cli.MavenCli.execute(MavenCli.java:906)
>         at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:283)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:206)
>         at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
>         at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>         at java.base/java.lang.reflect.Method.invoke(Method.java:568)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:255)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:201)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:361)
>         at 
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:314)
> Caused by: java.lang.IllegalArgumentException: Unknown NamedLockFactory name: 
> 'rwlock-redisson', known ones: [file-lock, rwlock-local, semaphore-local, 
> noop]
>         at 
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapterFactoryImpl.selectFactory(NamedLockFactoryAdapterFactoryImpl.java:197)
>         at 
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapterFactoryImpl.createAdapter(NamedLockFactoryAdapterFactoryImpl.java:157)
>         at 
> org.eclipse.aether.internal.impl.synccontext.named.NamedLockFactoryAdapterFactoryImpl.getAdapter(NamedLockFactoryAdapterFactoryImpl.java:147)
>         at 
> org.eclipse.aether.internal.impl.synccontext.DefaultSyncContextFactory.lambda$newInstance$0(DefaultSyncContextFactory.java:75)
>         at 
> org.eclipse.aether.DefaultSessionData.lambda$computeIfAbsent$0(DefaultSessionData.java:71)
>         at 
> java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1708)
>         at 
> org.eclipse.aether.DefaultSessionData.computeIfAbsent(DefaultSessionData.java:71)
>         at 
> org.eclipse.aether.internal.impl.synccontext.DefaultSyncContextFactory.newInstance(DefaultSyncContextFactory.java:75)
>         at 
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:251)
>         at 
> org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:243)
>         at 
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:278)
>         at 
> org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:172)
>         at 
> org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:1202)
>         at 
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:528)
>         at 
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:497)
>         at 
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:612)
>         at 
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:375)
>         at 
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:349)
>         at 
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:340)
>         at 
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:76)
>         at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:448)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:197)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:173)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:101)
>         ... 11 common frames omitted
> {code}
> see 
> [https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html]
> The same problem occurs with NamedLockFactory for "Hazelcast".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to