On 12/9/18 5:37 PM, Shawn McKinney wrote: > >> On Dec 8, 2018, at 10:04 AM, Stefan Seelmann <[email protected]> wrote: >> >> If time allows I'd suggest to follow the voluntary relocation. >> >> For Fortress, if you consider to merge the 4 repos into one, this would >> be a good time now. Just create a new "directory-fortress" repo at >> Gitbox [1] and merge the 4 into it, then request to delete the old >> repos, so no relocation needed. > > Trying to figure out how much work this is, and does it fit into my schedule > for the next few weeks... > > We’ll call your recommendation option one. A new repo gets created, say > directory-fortress, that would contain the four packages merged. That all > seems pretty straight-forward. What else must be done — would a new pom be > needed to drive the build/release of the four packages of the combined repo? > > In other words, does this change to combine the four into a single git > project repo force us to also change the structure (and process) of the maven > artifacts being built and released?
I'd say yes. The four old repos including their pom.xml reside then in a subdirectory each within the new repo (say core, realm, rest, web), then a new parent/aggregator pom.xml is needed in the new repo. The individual poms can then be cleaned up, i.e. redundant information (scm, issueManagement, developers, common parts of build, etc) can be moved up to the new parent pom. What is also required is to think about the license/notice files, likely they also need to be moved up to the new root. All in all not too hard, but for sure it requires some time to tweak the build and release. There is no need to rush, if it fits better into your schedule next year then postpone it. And to be clear, I hope it doesn't seem I want to force you to merge the 4 repos, if you feel more comfortable please keep them separate :) Kind Regards, Stefan
