Hi Niclas,
a few months ago I stumbled upon http://www.easyant.org/ .
Although I only played with the samples, it made a fairly
reasoned appeal. It leverages Ant and Ivy as the basic building
blocks and aims for, I cite:
<cite>
Our goals are :
* to leverage popularity and flexibility of Ant.
* to integrate Apache Ivy, such that the build system combines a
ready-to-use dependency manager.
* to simplify standard build types, such as building web
applications, JARs etc, by providing ready to use builds.
* to provide conventions and guidelines.
* to make plugging-in of fresh functionalities easy as writing
simple Ant scripts as Easyant plugins.
To still remain adaptable,
* Though Easyant comes with a lot of conventions, we never lock you in.
* Easyant allows you to easily extend existing modules or create
and use your own modules.
* Easyant makes migration from Ant very simple. Your legacy Ant
scripts could still be leveraged with Easyant.
</cite>
Cheers, Georg
Gang,
After these couple of days of struggling with Maven, *I* have finally
reached the breaking point and want to toss Maven out the window for
GOOD (trust me, it will be good). Someone else have already summarized
my feelings;
http://kent.spillner.org/blog/work/2009/11/14/java-build-tools.html
BUT, then what?? What choices do we have?
Looking at the needs we have;
* Module support and reuse across GIT repositories.
* Development work flow should be both fast and intuitive. And no
online checks for builds.
* Test workflow, unittest, performance tests, integration tests,
regressions tests are not the same thing and has different needs.
* Javadoc generation, packaging, merging, versioning, publishing.
* Test coverage measurement, reporting and publishing.
* Release Life Cycle management;
fork->dev->freeze->cut->review->sign->publish, and each of these have
their 'requirements'.
* Dependency & Version Management. Is Maven really doing the right
thing? How should it be done?
* Installer? (I have just received license for install4j from
ej-technologies (the JProfiler folks)).
Looking at the above, one could even ask; Is this really the scope for
a single tool?
In my pre-Maven life, I have used Make, Bash, Ant and even my own
creations. And these all have its pros and cons, and I one of the best
was "bash". Simple, straight forward and nothing that can't be done
fairly easily. But that makes Windows a 2nd class citizen. Should we
perhaps create a Java program to build our project? I know it sounds
really, really whacky and unnecessary, but...
This is definitely a favorite topic of discussion, so I am hoping to
receive a lot of flames, feedback, thoughts and suggestions...
Cheers
--
Niclas Hedhman, Software Developer
http://www.qi4j.org - New Energy for Java
I live here; http://tinyurl.com/2qq9er
I work here; http://tinyurl.com/2ymelc
I relax here; http://tinyurl.com/2cgsug
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
