[jira] [Created] (MNG-7237) Improve the accessibility of using the new named locks features

["Jacques-Etienne Beaudet (Jira)" <ji...@apache.org>]

Jacques-Etienne Beaudet created MNG-7237:
--------------------------------------------

             Summary: Improve the accessibility of using the new named locks features
                 Key: MNG-7237
                 URL: https://issues.apache.org/jira/browse/MNG-7237
             Project: Maven
          Issue Type: Improvement
            Reporter: Jacques-Etienne Beaudet


Currently, if you want to use named locks with Redisson for proper distributed locking of a maven repo, you have to download a bunch of jars and modify the m2.conf as described [here|https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html]. 

While this works fine, it is to me very cumbersome and will most likely hinder the adoption of the feature since it's not "built-in" maven nor it's a plugin you can just add to your project. Ideally, I wish we could just do 
{code:java}
mvn verify -T1C --named-lock-factory redisson-rwlock --named-lock-factory-config optional/config-file.yml
{code}
but as [~michael-o] mentioned [here|https://github.com/apache/maven-resolver/pull/122#discussion_r703332941], it seems like it's not possible. This issue is then to discuss about what's possible to improve the accessibility of this great feature that allows better usage of CI instances running multiple builds with a shared repo.

The options that Michael mentioned in the thread are the following : 
# Already add the config line in m2.conf by default
# Provide an additional binary distro based on a profile. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)