I think Maven is still very popular in the backend/enterprise development space, where it's been used for ages and "just works". It's stable, it's easy to maintain, and it does exactly what is needed from it without any fuss. But I also think that it's pretty common for Maven to just be a relatively small part of the overall build/deploy process for a Java project, and Jenkins or other CI platforms pick up where Maven drops off.
Gradle is a much more fully-rounded automation tool, and ideally, would handle the entire build/deploy pipeline and CI tools would only need to call Gradle once for the entire thing to go from source to production. If the entire build/deploy pipeline is in Gradle, then it is no longer a requirement for CI tools to run deploys, as you can still deploy locally if you need to, and you're less locked into a specific CI platform for its plugins.
Also it seems pretty rare that new frameworks/libraries are created using Maven, most new projects I see all use Gradle. This may very well be selection bias on my part as I live almost exclusively in the Android and Kotlin world where Gradle is the supreme ruler, but it does seem much more common for new projects to be created with Gradle. This leads me to believe that Gradle is actually the "de facto standard" over Maven these days.
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.
I think Maven is still very popular in the backend/enterprise development space, where it's been used for ages and "just works". It's stable, it's easy to maintain, and it does exactly what is needed from it without any fuss. But I also think that it's pretty common for Maven to just be a relatively small part of the overall build/deploy process for a Java project, and Jenkins or other CI platforms pick up where Maven drops off.
Gradle is a much more fully-rounded automation tool, and ideally, would handle the entire build/deploy pipeline and CI tools would only need to call Gradle once for the entire thing to go from source to production. If the entire build/deploy pipeline is in Gradle, then it is no longer a requirement for CI tools to run deploys, as you can still deploy locally if you need to, and you're less locked into a specific CI platform for its plugins.
Also it seems pretty rare that new frameworks/libraries are created using Maven, most new projects I see all use Gradle. This may very well be selection bias on my part as I live almost exclusively in the Android and Kotlin world where Gradle is the supreme ruler, but it does seem much more common for new projects to be created with Gradle. This leads me to believe that Gradle is actually the "de facto standard" over Maven these days.