+1 from me. Gradle might have its benefits but not in its current state and I don't know it well enough to commit to fixing it.
IIRC Lari and Matteo were proponents of gradle during one of the recent Pulsar community meetings. Search for "gradle" in Meeting Notes <https://www.google.com/url?q=https://docs.google.com/document/d/19dXkVXeU2q_nHmkG8zURjKnYlvD96TbKf5KjYyASsOE/edit&sa=D&source=calendar&ust=1651599874669558&usg=AOvVaw1tTF4s87Vbfo1ETHmJXjmw> . I think we should give them an opportunity to talk on this issue before moving forward with removal. On Thu, Apr 28, 2022 at 6:15 AM Nicolò Boschi <boschi1...@gmail.com> wrote: > +1 for removing Gradle > > We still have not figured out how to replace the release process using > Gradle and we have other issues and no one actually volunteered to fix > them. > > Nicolò Boschi > > > Il giorno gio 28 apr 2022 alle ore 08:31 Enrico Olivelli < > eolive...@gmail.com> ha scritto: > > > Il giorno gio 28 apr 2022 alle ore 04:26 ZhangJian He > > <shoot...@gmail.com> ha scritto: > > > > > > Hello, everyone. After talking with enrico and nicolo. I want to start > a > > > discussion about building systems. > > > We are now maintaining two build systems, I don't think that we want to > > > maintain both `maven` and `gradle`. > > > > > > I think that we need to decide to keep maven or gradle in the future. > > > > > > Personally, I tend to use maven, the main reason is that we don't have > > > active gradle experts now and gradle still has problems to solve. > > > > +1 > > I think we can keep Maven and remove Gradle. > > I see no strong reason to keep Gradle, > > it looks like the initial energy put into the migration faded away and > > we have no one who has time to work on it > > > > Enrico > > > -- Andrey Yegorov
