-1 for reverting back to Maven. Let's fix the issues in the Gradle instead of bringing Maven back. It will be a burden to maintain 2 builds systems in a single project. That's why it should be either Gradle or Maven, not both. I prefer Gradle and I can volunteer in resolving the issues that there are with Gradle.
-Lari On Mon, Mar 21, 2022 at 3:31 PM Enrico Olivelli <eolive...@gmail.com> wrote: > I see that the source tarball has a wrong name in current master > > I filed this issue, I believe it is a problem for a release > https://github.com/apache/bookkeeper/issues/3129 > > I am also facing other problems with the Gradle build here > https://github.com/apache/bookkeeper/pull/3084 > I am not able to exclude LogBack and some Netty modules imported by > ZooKeeper, > I see that we are importing dependencies using "dependency.create" and > I don't find much documentation about this. > > When I build locally BK I see many warnings from Gradle, like: > "Expiring Daemon because JVM heap space is exhausted" or > or > > Gradle detected a problem with the following location: > > '/Users/enrico.olivelli/dev/bookkeeper/bookkeeper-dist/build/distributions/bookkeeper-4.15.0-SNAPSHOT-src-bin.tar.gz'. > Reason: Task ':bookkeeper-dist-src:distTarSha512' uses this output of > task ':bookkeeper-dist:distTar' without declaring an explicit or > implicit dependency. This can lead to incorrect results being > produced, depending on what order the tasks are executed > > > This Gradle migration is basically blocking the release and we are very > late. > > IIUC there was some part of the community who pushed hard to do this > migration, but all the enthusiasm seems to have gone away and now we > have a broken repository. > > I wonder if it would be better to roll back to Maven, we didn't > refactor the repository and restoring the pom.xml files may not be so > hard as fixing all the Gradle problems. > > > > > Enrico >
