OK, let’s not rename to core. After we have removed the “calcite-“ prefix, the module in the “avatica” directory will be called “avatica-parent” and the module in the “avatica/core” directory will be called “avatica”.
Julian > On Mar 8, 2016, at 12:16 PM, Josh Elser <[email protected]> wrote: > > +1 works for me. > > I'm undecided on avatica-core. Eventually, I think it should be split into an > API and Client module, but, for now, I figured "core" is at least generic > enough. I'm happy to entertain any other name suggestions. > > Julian Hyde wrote: >> On Tue, Mar 8, 2016 at 7:00 AM, Josh Elser<[email protected]> wrote: >>> I did intentionally change the groupId, but I'm not stuck on it. I figured >>> it would be nice to have a single groupId which contains all of Avatica. >> >> Let's talk about maven module names. It will be difficult to change >> them after the release. >> >> I like the idea of avatica modules having groupId >> "org.apache.calcite.avatica". >> >> Currently their names are prefixed "calcite-avatica-", e.g. >> "calcite-avatica", "calcite-avatica-server", >> "calcite-avatica-metrics-dropwizardmetrics3". "calcite-avatica-noop". >> I think we should remove the "calcite-" prefix, hence "avatica", >> "avatica-server", "avatica-metrics", >> "avatica-metrics-dropwizardmetrics3", "avatica-noop". Each module >> would still have "Apache Calcite" in its name, for example "Apache >> Calcite Avatica Server", and of course in its groupId. What do you >> think? >> >> Also, should we rename "avatica" to "avatica-core"? Less sure about that one. >> >> Julian
