On Sun, Dec 28, 2025, 07:29 Ryan Schmitt <[email protected]> wrote:
> On Sun, Dec 28, 2025 at 5:23 AM Oleg Kalnichevski <[email protected]> > wrote: > > > > > Having Gradle as a secondary build tool could work, but it would mean > > extra work for me as a release manager as version information in Gradle > > files would need to be updated and tested at release time. And I _hate_ > > the ASF release process as is without having a secondary build system to > > worry about. > > > Tell me more. By "version information," do you mean all the dependency > management info? Or the httpcomponents versions themselves, and the logic > to generate `version.properties`? > > The way I'm thinking about this is that the Gradle build should have no > involvement in the release process at all, it would just be for local > development and testing. So you want to have two 2 build systems? We use Maven, there's no reason to add another. Gary For example, we could define additional test > targets that run the tests across multiple Java versions, with different > combinations of dependencies (to detect incorrectly modeled "optional" > dependencies), or with newer versions of `core` (to detect breaking > behavioral changes). > > It might be worth having a thread about what improvements we'd like to see > in the build system. Whether we add Gradle support, upgrade to Maven 4, or > both, we're going to be getting new, useful capabilities. >
