That would certainly make local development, PR builds, and the individual component releases easier. However, if each release requires a release of every sub-component, that would be harder to track.
I'm in favor of splitting out composable pieces, but we should be cognizant of process changes. Perhaps adapting the process to support this sort of thing, where it's currently easiest to put new components into a single repo/component and Volkan found while working on the maven shadow plugin. -ck On Fri, Feb 11, 2022, at 10:37, Gary Gregory wrote: > WRT bloat, we could take the Maven approach and migrate some features to > separate repositories on their own lifecycles. I'm generally not that fan > due to the extra churn but it might be worth considering. > > Gary
