apache / apache/maven-resolver
Drop Hazelcast named locks
Open
breaking
- Dominant language
- Java
- Stars
- 152
- Forks
- 160
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
This is to be happen in 2.1 or alike version change.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating Hazelcast named-lock usage in the Java code and reviewing how locking is integrated; clarify the target release and removal scope before making changes. Done should mean named locks are removed without breaking the resolver's locking behavior, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100