commit | 725edd7fa6661b60bfec9caa2a8176aabd523cfa | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Thu Feb 22 16:45:38 2024 +0100 |
committer | GitHub <noreply@github.com> | Thu Feb 22 16:45:38 2024 +0100 |
tree | 0d2e537cd44261c7b5ee6a3f61de31c99d1e75ed | |
parent | 393d77c0631de11f0e6832511129030b5dd578be [diff] |
[MRESOLVER-421] Extend NamedLock API to make possible 1..n lock to name (#431) This PR implements MRESOLVER-421, basically allowing not only 1:1 resource to lock mapping as Named Locks were originally incepted. Also, change lock name to dedicated "key" type, and this improves tremendously logging and diagnostic (ie. if you used hashing name mapper, good luck to tell what artifact it was). This PR also adds tests to Redisson as there were no tests in the module since its inception. --- https://issues.apache.org/jira/browse/MRESOLVER-421
You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us:
git diff --check
before committing.[MRESOLVER-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verify
to assure nothing else was accidentally broken.If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.