See inline
On Tue, Feb 10, 2015 at 9:20 AM, Vladimir Sitnikov < [email protected]> wrote: > Well, isn't Calcite a consumer of Guava, jackson, etc, etc? > Yes. And if they expose newly incompatible dependencies, then Calcite would be forced to shade them. > > It is not that good if minor release of Calcite would force consumers > to implement shading if it was not required previously. That is a fair point. Perhaps this is an argument that the dependencies that Calcite exposes to downstream consumers constitutes part of its API. Changes to that profile would require a major version change just like any other API changes.
