I'm not super familiar with Gradle yet, but here are my thoughts: - It can't be any worse than make. I mean, $$($(1)-deb). I'd much prefer debugging a more modern language, and as Cos points out, it's intended for a JVM ecosystem but can do other things when needed. - I'd prefer we leave Make around for perhaps one more release just to really solidify the Gradle system a bit more. However if we keep it deprecated, I see no point in "maintaining" both, meaning that if people want to add new features to the build (several JIRAs going on for that right now) - there's no need to keep adding that to the Makefile, let's just keep the versions and metadata for new projects up to date. I don't believe we routinely run into bugs, so I doubt much work will have to be put in outside of bigtop.mk.
On Fri, Jul 11, 2014 at 11:54 PM, Roman Shaposhnik <ro...@shaposhnik.org> wrote: > On Fri, Jul 11, 2014 at 6:01 PM, Konstantin Boudnik <c...@apache.org> > wrote: > > I am temporarily putting the [VOTE] thread to halt and instead starting > > [DISCUSS]. Per Jay's: > > > > BIGTOP-1314 highlights the fact that we now have 2 build systems: > Makefile > > and build.gradle. And the fact that the Makefile approach is now > > deprecated. > > > > As per Mark's suggestion in that JIRA, the future of Makefile should be > > decided on the mailing list before the next JIRA comes out to further > > distance from Make and embrace gradle. > > > > Should we continue to support the Makefile builder? > > I'd be more than happy to get rid of it right after we release Bigtop 0.8.0 > > Thanks, > Roman. >
