Would you choose Maven Vs Ant + Ivy ?
Let's understand, what are the general expectation on a build library/solution ?
- Dependency management of libraries - Meaning, no need to keep the libraries/jars checked in to your repository, it can be as simple as defining in an external file Ex: Pom.xml / ivy.xml.
- Ability to build the application(.war, .ear etc.) - Meaning ability to write scripts to assemble/package an application. Ex: build.xml (Ant), assemble.xml (maven) etc.
Pros & Cons,
- With Maven less scripting, put the files in the right folder as indicated by the maven archetype.
- With Ant + Ivy, you still have to write your build file !!! Advantage is you can have a flexible folder structure & need not be restricted as in maven archetypes.
Think about it !!!
Comments & your experience most welcome !
How about gradle?. I hope gradle also simple to use. easy to manage dependencies. Also taken care of both expectation. Is it?
We use Gradle in my project, it's definitely a strong alternative to ant/maven.
Post a Comment