Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move Dependency functionality to other projects

Open
#33 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
java

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.

Description

enhancement
  • *Rule*, *Ribbon*, *LoadBalancer* and *Feign* to spring-cloud-netflix
  • *ZookeeperDependenc* to spring-cloud-commons minus Zookeeper
  • move watcher package to spring-cloud-commons, DefaultDependencyWatcher -> ZookeeperDependencyWatcher
  • watcher.presence has curator classes as part of the interface, so initial this won't move.
Dominant language
Java
Stars
574
Forks
407
Avg merge
11h 50m
Merged PRs (30d)
12

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from spring-cloud/spring-cloud-zookeeper

All issues in spring-cloud/spring-cloud-zookeeper

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.