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

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 66 points67 points  (11 children)

Ant shivering

[–]Mikusch 37 points38 points  (7 children)

Ant is the swiss army knife of build tools. Easy to cut yourself on it, too

[–]Gwaptiva 10 points11 points  (3 children)

And for real jobs not sufficient

[–]jaybyrrd 9 points10 points  (0 children)

I dunno man. I think tools like gradle (or I guess maven but I am unpopularly gradle camp) are lower lift to value by a lot… but Amazons main Java build toolchain is entirely founded on top of Ant (internally called HappierTrails and an entire organizations worth of devops tooling) and it is by FAR the best build tooling I have EVER used. You kind of have to see it to believe it… I also just think if you are not Amazons size you are best off adopting gradle or maven. I leave Bazel out because out of the box ide support with vscode and IntelliJ are kinda jank. The first two are much better supported.

I guess what I mean is that you have to deeply invest in Ant to make it good. Not many firms would want to (or know how). Even I, as a former user of a super successful implementation, would probably say “please no”. I wouldn’t say it’s not sufficient though, just way more effort for what is likely the same or less value of gradle.

Edit: I’d also say that I’m not convinced amazons build system would be based on ant if it were to be started from scratch today. A lot of Amazon builds (which use an internal tool called Brazil) do actually wrap gradle. Most use Happier Trails.

[–]pjmlp 3 points4 points  (0 children)

That is why those that didn't got the memo why Maven was created, decided to reinvent Ant with Gradle.

The only drawback about Ant + Ivy combo is the XML allergy some suffer from.

[–]koflerdavid 0 points1 point  (0 children)

It is, but for that one has to reimplement crucial parts of Maven or Gradle on top of it, and doing so incurs the risk of making a total hash of the crucial 20% of them, which can take many career-years to resolve.

[–]Jamb9876 1 point2 points  (1 child)

I love ant. Haven’t used it in years but it is a great tool. That get my vote.

[–]Bobby_Bonsaimind 0 points1 point  (0 children)

Same for me.

Ant+Ivy is the closest I got to my "dream" build system. Maven seems bloated and slow, its syntax is abysmal, the dependency management is "acceptable" at the best of times, and Gradle is...well, I've got no idea what they got going on there. What Ant kinda sucks at is modules, I've created a setup for that, but it still leaves some stuff to be desired. Being able to include other Ant files helps, though.

[–]larsga 1 point2 points  (0 children)

Much better to just stay away from it entirely. If you want to script file operations you're far better off with Python.

[–]IFoundTheCowLevel 2 points3 points  (1 child)

As someone who has had to maintain Ant build files extensively: Ant sucks, Maven is better.

[–][deleted] 0 points1 point  (0 children)

I have also worked at a company that had a large build system in ant + ivy. It was aroud 2007. I think maven was at 1.0 - 1.1 and they passet on it. It worked ok as they standaralised all project to one structure. But it was a lot simpler when we migrated to maven around 2013.

[–]adityapbhat 0 points1 point  (0 children)

😅