Yes, neither Git nor Maven is optimal for mono-repos since you can only
tag/branch the whole repo, and only have one version for the whole build.
Google have a big mono-repo, but they do not use Git, nor Maven.
I think we should release and version everything in one repo together,
otherwise it will get very messy.
On 2018-01-22 22:58, Matt Sicker wrote:
Using Maven profiles could help, though when tagging a release, if we
didn't release every module within, then it'd get out of sync anyways. Then
it would still require building every single component in each release,
even when said components haven't changed at all.
On 22 January 2018 at 15:50, Gary Gregory <garydgreg...@gmail.com> wrote:
Coming back around to the idea of One Repo to Rule Them All*TM* ... what if
we used Maven profiles to separate out the "main" build from "other"
builds?
All that is needed to move modules from one build to another is just to
edit the profile!
