spring-cloud / spring-cloud/spring-cloud-zookeeper
Move Dependency functionality to other projects
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 574
- Forks
- 408
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 4
Description
*Rule*,*Ribbon*,*LoadBalancer*and*Feign*tospring-cloud-netflix*ZookeeperDependenc*tospring-cloud-commonsminusZookeeper- move
watcherpackage tospring-cloud-commons,DefaultDependencyWatcher->ZookeeperDependencyWatcher watcher.presencehas curator classes as part of the interface, so initial this won't move.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the Rule, Ribbon, LoadBalancer, Feign, ZookeeperDependency, watcher, DefaultDependencyWatcher, and watcher.presence code, then compare the stated spring-cloud-netflix and spring-cloud-commons destinations. Done means the listed functionality is moved as specified, with curator-dependent watcher.presence left in place initially.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100