Improve isolation of bookkeeper core and extensions
- Dominant language
- Java
- Stars
- 2k
- Forks
- 976
- Avg merge
- 6d 15h
- Merged PRs (30d)
- 7
Description
Currently we have the -Dstream profile, which turns on the building of a bunch of "optional" extensions. However, when we test and when we release, we always enable the profile, so the isolation of the extensions is incomplete and never tested.
- [ ] add blurb about the different components and how to compile in the README.md
- [ ] check that the build documentation for the website is complete
- [ ] add a switch to enable stream profile with -Dall
- [ ] -all binary package should only be built with when -Dall is specified
- [ ] current integration tests should be run without the stream profile
- [ ] move -Pstream specific integration tests to separate directory
- [ ] docker testing image using -all (currently they all use -server)
- [ ] add a integration smoke test to test basic bookkeeper-server functionallity using -all package (with -Pstream)
Contributor guide
Assessment
This issue has not been assessed yet.