Gradle provides all the benefits of Maven (build conventions, plugin ecosystem, dependency management, and nested builds) without the need for rigid adherence to arbitrary conventions. A greenfield Gradle project can benefit by sticking with defaults that are sensible and a brownfield project can create configuration customizations that will allow you to port virtually any build structure to Gradle with minimal effort.
Gradle's only weak points are where the build system is so flexible that at times it is hard to track where your changes mess with established documentation (in these cases you've sort of made your own bed so it's your own fault for getting so far off track). Most of the major IDE's support Gradle so the tooling is already there. Over all, Ithere is no other build system I would choose to start a new project with and there are very few legacy projects that wouldn't benefit from getting upgraded to a gradle build.