We have spent a lot of time discussing this topic than actually trying to arrive at a decision.
Everyone has a strong opinion about which build tool the project should use. Each tool has its strengths and weaknesses. Today, `gradle` is the best tool for Java based projects in _my_ experience. Is it perfect? No. Each tool will have some weaknesses and _all_ of them have a learning curve. However, 90% of our use-case is to add or change existing dependencies, producing artifacts and triggering test runs. For this most build tools are fine. They have a very tiny learning curve for these activities. The rest 10% is going to be complicated and will require research no matter what tool you end up picking. This is true for ant as well. If anybody wants to drive this forward, we should enumerate the tools & associated pros/cons. Dinesh > On Feb 4, 2022, at 4:44 AM, Mick Semb Wever <m...@apache.org> wrote: > > > > I think that it is not only about the build tool as such. There is a > lot of scripting involved in build scripts as well as in Jenkins > pipeline and so on. > > > Seconding this. Rewriting the build system is the easy bit. The ecosystem > (CI, releases, ccm, etc) is involved and not versioned (expects all branches > to work in the same way). Not impossible, or even challenging, but def > involved. >
