[GitHub] [maven] cstamas opened a new pull request, #761: [EXPERIMENT] Resolver locking mode set from Maven

[GitBox <gi...@apache.org>]

cstamas opened a new pull request, #761:
URL: https://github.com/apache/maven/pull/761

   Requires https://github.com/apache/maven-resolver/pull/188
   
   The idea is similar as with resolver transport: add simple(er) switches to maven to control resolver locking aspect. Just as with transport (setting priority), setting proper locking may be cumbersome, as it requires lock factory but also name mapper settings, and there are even pairings that are must (like for file). Instead of relying directly on https://maven.apache.org/resolver/configuration.html here, again as in case of transport, offer a "higher" level settings from Maven itself:
   * file
   * local
   * hazelcast
   * redisson
   
   That provides OOTB "experience" to end users (naturally  in case of latter two needed configuration and remote services are assumed but not checked for!).
   
   Hence, `mvn -Dmaven.resolver.locking=file ...` would make Maven use file locking. 
   


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [maven] cstamas closed pull request #761: [EXPERIMENT] Resolver locking mode set from Maven

[GitBox <gi...@apache.org>]

cstamas closed pull request #761: [EXPERIMENT] Resolver locking mode set from Maven
URL: https://github.com/apache/maven/pull/761


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org