Look, if you have a lot of pre-existing Maven builds then of course the story gets more complicated. Large enterprises usually have higher priorities than spending large $X on any kind of migration that's not absolutely necessary, including the costs for retraining dozens or hundreds or thousands of developers to use a new build tool and to overhaul tooling that was built on top of the old solution (e.g. deployment scripts invoking mvn deploy and Maven reports), and can often result in choosing options that are technically worse but organizationally better.

What I mean is when you have the freedom to choose a new technology stack because it's a new project - because a lot of companies still won't give you that freedom even with new projects.

Unless you have some objection against Gradle itself?