> On Dec 9, 2018, at 11:08 AM, Stefan Seelmann <[email protected]> wrote: > > On 12/9/18 5:37 PM, Shawn McKinney wrote: >> >> 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.
Agreed. > > On Dec 9, 2018, at 11:08 AM, Stefan Seelmann <[email protected]> wrote: > > 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 :) For the record, I’m in favor of combining the four so your comments are well received. I’ll give it a few days, to think about. Thanks for weighing in. —Shawn
signature.asc
Description: Message signed with OpenPGP
