Any opinions on whether we should formalize into some kind of release
verification step (manual or automatic)?
On Thu, Dec 2, 2021 at 5:22 PM Julian Hyde <jhyde.apa...@gmail.com> wrote:
> It’s quite easy to script. For example,
>
> git checkout calcite-1.27.0
> ./gradlew dependencies > /tmp/d27.txt
> git checkout calcite-1.28.0
> ./gradlew dependencies > /tmp/d28.txt
> diff /tmp/d2{7,8}.txt
>
> I posted the output at
> https://gist.github.com/julianhyde/9ca5915bfb91494b7f91405ad15d698e <
> https://gist.github.com/julianhyde/9ca5915bfb91494b7f91405ad15d698e>.
>
> Julian
>
>
> > On Nov 30, 2021, at 3:40 PM, Jacques Nadeau <jacq...@apache.org> wrote:
> >
> > 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 <zabe...@gmail.com>
> > 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 <jacq...@apache.org>
> wrote:
> >>
> >>> Can you file a JIRA? We should address before 1.29.
> >>>
> >>> On Tue, Nov 30, 2021 at 6:40 AM Zoltan Farkas
> >> <zolyfar...@yahoo.com.invalid
> >>>>
> >>> 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 <
> >>>> sitnikov.vladi...@gmail.com> wrote:
> >>>>>
> >>>>>> since core/src/kotlin does not exist yet.
> >>>>>
> >>>>> I mean core/src/main/kotlin does not exist yet
> >>>>>
> >>>>> Vladimir
> >>>>
> >>>>
> >>>
> >>
>
>
