Split centraldogma-server module
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
This idea was suggested by @ikhoon.
The `centraldogma-testing` module depends on the `centradogma-server` module which has ZooKeeper dependency.
However, users don't need the replication feature for Central Dogma server and sometimes the ZooKeeper dependency causes a dependency conflict with other libraries.
So it would be nice to split `centraldogma-server` module into two, one that has a replication feature and one that doesn't have it.
```
- centraldogma-server
- centraldogma-server-standalone
- centraldogma-server-replication
- centraldogma-testing
- centraldogma-server-standalone
```
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
Start by mapping the dependency declarations for centraldogma-server and centraldogma-testing. Separate the replication-related ZooKeeper dependency from the standalone server module as outlined in the issue, then verify that centraldogma-testing depends on the standalone module and that replication remains available in its dedicated module.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100