[STORM-3533] Make a distinct storm-ras artifact
- Dominant language
- Java
- Stars
- 6.7k
- Forks
- 4k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 62
Description
Storm 2.0.0 release page here suggest us to put storm-server as test scope for testing. But RAS packages are in storm-server package too, and we need it when we launch our topology. Some of RAS packages should be either integrated in storm-core or in a distinct package storm-ras, so that we do not have to put storm-server as compile test, which we do for now.
---
Originally reported by antoine.tran, imported from: Make a distinct storm-ras artifact
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by examining the storm-server artifact and locating the RAS packages that are needed when launching a topology. Review the artifact and dependency configuration to determine what belongs in a distinct storm-ras package. Done means RAS packages are available without requiring storm-server as a compile-time test dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100