Sorry, one important clarification: These are not decided yet, in the contrary, the main goal would be to have a discussion about these (and more) points and arrive to a mutual agreement on how we should do the migration, and to make sure this will not die and forgotten in a pull request somewhere.
Norbert On Tue, May 29, 2018 at 4:12 PM Norbert Kalmar <nkal...@cloudera.com> wrote: > Thanks Andor! > > A quick update on where were at with the maven migration plan: > - All 3 active branches will get the full maven build. > - End artifacts will change, 3 separate jar for server, client and common, > possible package change as well (backward compatibility will break) > - The changes will be committed to master / 3.5 / 3.4 in smaller > iterations, starting with moving the docs to it's new folder > > Check out the docs for more info, and some explanation why we arrived to > the above conclusions in the above statements. > The link again: > https://docs.google.com/document/d/1WXqhaPlCwchcWc8RCEzbCmVa4WbBDlfR3GQngikGjqc/edit?usp=sharing > > Regards, > Norbert > > On Mon, May 28, 2018 at 1:09 PM Andor Molnar <an...@cloudera.com> wrote: > >> Excellent job Norbert, this doc will be very useful to discuss all kinds >> of >> aspects of the migration. >> I've left some comments already. >> >> Thanks, >> Andor >> >> >> >> On Fri, May 25, 2018 at 3:14 PM, Norbert Kalmar <nkal...@cloudera.com> >> wrote: >> >> > Hi, >> > >> > After doing some proof of work and had some discussion, I have created a >> > google docs about the maven migration. >> > >> > Please read through, and comment your thoughts and suggestions. >> > >> > https://docs.google.com/document/d/1WXqhaPlCwchcWc8RCEzbCmVa4WbBD >> > lfR3GQngikGjqc/edit?usp=sharing >> > >> > >> > Thanks! >> > Norbert >> > >> >
