You can effectively implement your entire CD pipeline with Gradle. Maven, at least in my experience, is much more centered around just the build process (compile the code, run tests, bundle up your JAR/WAR).
In every team I've worked on so far, there is some external CD pipeline like Jenkins, GitHub Actions, Gitlab Pipelines, or something else that teams use to actually deploy software. Dedicated CD pipeline tools are very effective at managing and visualizing pipelines and stages, so the extra complexity of Gradle that enables it's fancy features just aren't a compelling selling point. So my opinion on Gradle vs Maven comes down to "doesn't really matter, just give me a command that can compile my code and run unit tests".
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You can effectively implement your entire CD pipeline with Gradle. Maven, at least in my experience, is much more centered around just the build process (compile the code, run tests, bundle up your JAR/WAR).
In every team I've worked on so far, there is some external CD pipeline like Jenkins, GitHub Actions, Gitlab Pipelines, or something else that teams use to actually deploy software. Dedicated CD pipeline tools are very effective at managing and visualizing pipelines and stages, so the extra complexity of Gradle that enables it's fancy features just aren't a compelling selling point. So my opinion on Gradle vs Maven comes down to "doesn't really matter, just give me a command that can compile my code and run unit tests".