Good idea. We will create Github issues to track progress of the Gradle migration and activation to help people contribute to it.
- Henry On Thu, Sep 16, 2021 at 11:44 PM Nicolò Boschi <boschi1...@gmail.com> wrote: > Henry, thank you for the update > > I think it would be a good idea to create a GH issue in order to track all > next steps needed to remove maven from the project; in this way other > contributors (e.g. me) can help speeding up the implementation > > Nicolò Boschi > > Il giorno gio 16 set 2021 alle ore 19:49 Henry Saputra < > henry.sapu...@gmail.com> ha scritto: > > > HI Nicolo, > > > > I agree these double dependencies updating for Maven and Gradle are not > > ideal. > > We will start working on adding Github actions to use gradle to run int > > tests. Once the actions are active and working, we can start removing > Maven > > as the build tool for BK. > > > > Sincerely apologize for the delay in this process. > > > > - Henry > > > > On Tue, Sep 14, 2021 at 6:38 AM Nicolò Boschi <boschi1...@gmail.com> > > wrote: > > > > > Hi all, > > > > > > I would like to know what is the current status of BP-43 (gradle > > > migration), I see all the related issue closed on Github > > > > > > I think until we have both Maven and Gradle the build process is not > > clear > > > I see we have double dependencies declaration and it is much > error-prone > > > while upgrading libraries and similar (also i found > > > > > > I'd like to know what steps are missing and if someone is putting > effort > > on > > > finishing it > > > > > > Regards > > > > > >
