Another very interesting option is Gradle : http://www.gradle.org/
It's Ant + Ivy with predefined build rules through plugins (java, war,
maven-deploy, etc).
The build script can be entirely declarative (and ultra-compact compared
to Maven) if you don't have specific needs, but it's actually a Groovy
script and is wide open to custom rules and plugin parameterization and
extension if there are specific build needs. It also has strong support
for multi-project builds.
I've been using Gradle for my recent projets and I'm quite happy with it
: simple and straightforward for standard needs, and doesn't make you
bang your head against the wall (i.e. write a Maven plugin) for specific
needs.
My 2 cents,
Sylvain
Le 07/04/11 10:50, Ate Douma a écrit :
As we're about to bootstrap the new Rave code base, it would be good
to decide now what build engine we will use. This choice will have
impact on how we structure and configure our source tree, build, test
and integration environments.
As a Java based project I think we have three options:
- Ant
- Ant/Ivy
- Maven
OSEC is Ant based, OGCE, SURFNet and Shindig are Maven based, Wookie
uses Ant/Ivy.
I have a strong preference to use Maven as I'm using that for almost
every other project already and IMO has nowadays the strongest
(automated) ASF infrastructure support. But for those not accustomed
to Maven this might require some learning curve to get used to as
Maven does have specific restrictions and requirements, not the least
concerning structure and layout of the source tree itself.
So I'd like to hear the preference of the other developers.
If Ant or Ant/Ivy turns out to have the biggest support, I'm fine with
that as well.
Ate
--
Sylvain Wallez - http://bluxte.net
