Nice. Anyone know if there is a tool to fingerprint dependencies between releases so we can avoid introducing new dependencies accidentally?
On Tue, Nov 30, 2021 at 1:26 PM Stamatis Zampetakis <[email protected]> wrote: > It seems that Vladimir fixed this already in [1]. > > [1] > > https://github.com/apache/calcite/commit/f3e2f041567e35e65464676d3171db3b5f2ddf9c > > On Tue, Nov 30, 2021 at 7:50 PM Jacques Nadeau <[email protected]> wrote: > > > Can you file a JIRA? We should address before 1.29. > > > > On Tue, Nov 30, 2021 at 6:40 AM Zoltan Farkas > <[email protected] > > > > > wrote: > > > > > According to the published pom it is a direct dependency: > > > > > > https://repo1.maven.org/maven2/org/apache/calcite/calcite-core/1.28.0/calcite-core-1.28.0.pom > > > < > > > > > > https://repo1.maven.org/maven2/org/apache/calcite/calcite-core/1.28.0/calcite-core-1.28.0.pom > > > > > > > > > > > > > > On Nov 29, 2021, at 11:41 PM, Vladimir Sitnikov < > > > [email protected]> wrote: > > > > > > > >> since core/src/kotlin does not exist yet. > > > > > > > > I mean core/src/main/kotlin does not exist yet > > > > > > > > Vladimir > > > > > > > > >
