I would be for 1) where 2) is just a beneficial consequence of doing so. 1) is the fastest way to be done with it, most bang for the buck.
Also, 1) does not exclude 3) down the road, it just streamlines it more comfortably. Accord is on Gradle already, we first quickly introduce Jamm as another one, being it Maven ... whatever. But the goal is completed, right? Then when 3) is due we might just rewrite Jamm on Maven to Gradle and after doing so I can imagine that converting submodules (which are on Gradle already) to one uber Gradle build is _way more easier_ than trying to do it at the same time. On Tue, Jan 6, 2026 at 2:48 PM Josh McKenzie <[email protected]> wrote: > > So: > - Non-controversial / roughest workflow: take it in as a submodule. Make a > case for build system changes separately if at all. Continue to bend ant to > our will - against its will. > - Mid-controversial / smoother workflow: take in as submodule, shift build > system to something modern w/better support. > - Most controversial / smoothest workflow: take jamm in natively and take on > a new build system piece with it (maven which it has, or migrate to gradle > which would be new) > > I'm actually willing to make the case for the 3rd option; let me follow up > with Bernardo today since he drove a lot of prep work on that front and I'll > bring it to the list here on a new thread referencing this. Worst-case the > build system discussion hits a rapid clear wall and we decouple the topics, > get jamm as a submodule, and hash through the build system discussion > separately. > > On Tue, Jan 6, 2026, at 9:13 AM, Brandon Williams wrote: > > On Tue, Jan 6, 2026 at 8:09 AM Štefan Miklošovič <[email protected]> > wrote: > > However, I would like to eventually see that the build systems converge and > > we could rewrite > > it later on to Gradle to copy how Accord has it. > > Changing build systems has been a non-starter for many years now, so > my hope is we make some kind of incremental progress like this and > reach a point where we finally take the plunge and transition fully to > one build system. Either because it makes sense or out of frustration > with dealing with all of them. > > Kind Regards, > Brandon > >
