[
https://issues.apache.org/jira/browse/MRESOLVER-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17376821#comment-17376821
]
Michael Osipov commented on MRESOLVER-188:
------------------------------------------
Will add https://github.com/jebeaudet as reviewer on GH when my PR is done.
> Improve documentation on using the named locks with redis/hazelcast
> -------------------------------------------------------------------
>
> Key: MRESOLVER-188
> URL: https://issues.apache.org/jira/browse/MRESOLVER-188
> Project: Maven Resolver
> Issue Type: Task
> Reporter: Jacques-Etienne Beaudet
> Assignee: Michael Osipov
> Priority: Minor
>
> Following a discussion on [https://github.com/apache/maven-resolver/pull/68.]
> The
> [documentation|https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html]
> to use the named locks with redis/hazelcast is a bit lacking. Here is what
> is missing IMHO :
> # A notice to say that using the named locks with redis/hazelcast is not
> compatible with the latest version of maven 3.8.1 since this version of maven
> uses maven-resolver 1.6.x and the API is incompatible with 1.7.x. We could
> also mention why mvn 3.8.x cannot support 1.7.x.
> # Add the step to to actually activate the redis locks with an example (`mvn
> compile -Daether.syncContext.named.factory=rwlock-redisson`)
> # Add a section to enable debug logs
> # A link to the 1.6.x documentation so that people that want to use it with
> mvn 3.8.1 can follow
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
