views:

3157

answers:

4

If there is Maven does it at all make sense to learn and use Ant?

+1  A: 

This article will probably clarify things for you:

Excerpt:

Ant and Maven are different. Maven is not just a building tool, it provide an organization and a structure layer. All you do in ant can be done in Maven because you can call ant target.

ojblass
+1  A: 

yes, two main reasons:

  1. Ant is the underlining engine that makes maven work
  2. Ant unlike Maven is straightforward and simple - learning the basics is a matter of minutes not hours.

two minor reasons:

  1. A lot of other projects use Ant and you might need to tinker with their build process.
  2. What happens when you need to extend Maven, from what I know this can be done via extending Ant
KingInk
re main #1: see section "What Maven is not" at http://maven.apache.org/what-is-maven.html . You can use the ant plugin (e.g. ant:ant to create a build.xml) but otherwise, maven is exclusive of antre minor #2: or by writing maven plugins. using ant tasks in-line works too but is more imperative
whaley
One correction - maven 2 is not built on Ant, this was true for maven 1 only
David Rabinowitz
you learn a new thing everyday, thanks guys
KingInk
actually it wasn't true for m1 either.. it's always been a separate codebase that Jason started working on as part of the Jakarta project.
Brian Fox
separate codebase as in a fork or separate codebase as new code?I might be wrong but I always believed one can extend maven with ant tasks and so I thought they are using more or less the code.
KingInk