Haven't used any, somehow missed the Eclipse and idea :) I Wonder the opinion of more qualified people. My research showed that the mainstream is ant and maven. Also a lot of articles appear about gradle.
About the last I read the documentation, samples, and quick start guide, liked the idea, however, immediately to deal failed. More precisely, failed to find the code samples needed to create a build script a simple project
a couple of external libraries :)
Also honored docks ant and maven, but I don't really like the idea of configuration via xml, I would like just to write code in any sane language, as implemented, for example, in gradle.
Please advice on what Tula is still to stay and understand more deeply? It is clear that you need to know ideally all, but work all the same with any one, moreover, special requirements to the build system no.
The idea of Maven, I think, very cool — a descriptive view of the Assembly-
ie I have a project that depends on it, and that you — now build it!
Need to get used to this approach, in comparison with the build as a sequence of actions, but if doing nothing is not standard, this approach saves a lot of time to You, and to those who then Your Assembly meets.
If a non-standard lot, you can look at gradle is a Maven in Groovy instead of XML — i.e., until everything is standard use a descriptive style, and when necessary, write pieces of the script in Groovy
Edwin_Rice44 answered on October 10th 19 at 13:26
You can use ant+ivy. A bunch of all — powerful ant almost omnipotent in terms of build and all that goes with it. And ivy — ecologic dependencies. The idea, accordingly, press once on the build ant script, and then configure it to work with ivy.