cstamas commented on code in PR #196:
URL: https://github.com/apache/maven-resolver/pull/196#discussion_r979314241


##########
maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/synccontext/DefaultSyncContextFactory.java:
##########
@@ -130,18 +130,18 @@ public SyncContext newInstance( final 
RepositorySystemSession session, final boo
 
     private NamedLockFactoryAdapter createAdapter( final 
RepositorySystemSession session )
     {
-        String nameMapperName = ConfigUtils.getString( session, 
DEFAULT_NAME_MAPPER, NAME_MAPPER_KEY );
-        String namedLockFactoryName = ConfigUtils.getString( session, 
DEFAULT_FACTORY, FACTORY_KEY );
+        String nameMapperName = ConfigUtils.getString( session, 
DEFAULT_NAME_MAPPER_NAME, NAME_MAPPER_KEY );
+        String namedLockFactoryName = ConfigUtils.getString( session, 
DEFAULT_FACTORY_NAME, FACTORY_KEY );
         NameMapper nameMapper = nameMappers.get( nameMapperName );
         if ( nameMapper == null )
         {
-            throw new IllegalArgumentException( "Unknown NameMapper name: " + 
namedLockFactoryName
+            throw new IllegalArgumentException( "Unknown nameMapperName: " + 
namedLockFactoryName
                     + ", known ones: " + nameMappers.keySet() );
         }
         NamedLockFactory namedLockFactory = namedLockFactories.get( 
namedLockFactoryName );
         if ( namedLockFactory == null )
         {
-            throw new IllegalArgumentException( "Unknown NamedLockFactory 
name: " + namedLockFactoryName
+            throw new IllegalArgumentException( "Unknown namedLockFactory: " + 
namedLockFactoryName

Review Comment:
   I just figured the problem you reported in original related comment, fixed, 
and returned messages as were, the variables were mixed uo



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to