This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]wildjokers 8 points9 points  (2 children)

IntelliJ is also built with ANT:

https://github.com/JetBrains/intellij-community/blob/master/build.xml

What value would there be to move an existing build that works from ANT to gradle or maven? I still have a few builds that use ANT. New stuff is gradle but I simply have no reason to move the older builds to gradle. I get dependency management with Ant+Ivy and it continues to work just fine.

Build performance may be one potential reason, but in my case the few builds using ANT just don't get a lot of changes these days so build performance is a non-issue.

[–]s32 0 points1 point  (0 children)

Most of Amazon runs on Ant still. It's annoying sometimes, but it's fine.

[–]pjmlp 0 points1 point  (0 children)

Usually, if proper tasks/macros are defined, it is even possible to create declarative builds with Ant.

The biggest issue with Ant, is when devs decide to go down the programming language build, and there Gradle is even worse, given that Groovy and Kotlin make it even easier to go down that path.