Maven, one of the another build tool, which got most popularity after Ant and it also came with dependency management solution to the problem that the users were facing in Ant. The first problem in Ant was imperative programing where user has to write lots of boiler plate code. Another problem was dependency management. Ant does not have any in-built dependency management solution (Ant later integrated with Ivy for dependency management). A user has to write each and every JAR file path in the build file that it needs to download, and in case of transitive dependencies, it is too complex for the user to identify each and every dependent JAR and mention the JAR name in the build file. Also, in case of version conflicts, it consumes lots of a developer's efforts. Maven came with the declarative programing model and in-built dependency management solution. Gradle is also built on the top of these principles; thus, migrating from Maven to Gradle seems very comfortable...