> On Jan 22, 2018, at 3:23 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > On Mon, Jan 22, 2018 at 2:58 PM, Matt Sicker <boa...@gmail.com> 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. >> > > I just tried using profiles to define the main modules and extra ones. It > works like a charm. This allows us to move modules around very easily, > except that nothing is 'moving'. Further thoughts?
While you can create profiles to include certain modules for certain purposes (we currently only build the log4j-distribution when the “apache-release” profile is active) that definitely will not work for releases. The problem is the version numbers get incremented by the release plugin and trying to release only parts of the tree will get the version numbers all out of whack. Ralph
