ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: Ant+Ivy session at Apache Barcamp
Date Sun, 07 Nov 2010 06:28:09 GMT
On 2010-11-02, Antoine Levy Lambert wrote:

> - why do we not ship ant and ivy together ?

To some people our current distributions are too big already 8-)

There certainly is room for additional distribution formats like "the
latest Ant bundled with the latest Ivy" that could be released whenever
Ant or Ivy is released or "Ant plus the latest releases of selected
Antlibs" or ...

Those things don't necessarily need to be part of our usual releases but
could be put together separately.

In case of "latest releases" bundles, formally we wouldn't even need to
vote on them.  In theory (and legaly) what we vote on is the source code
we release and the binaries are only created for our users' convenience.

> - which support is there in ant to take advantage of multicore
> machines to do work in parallel ?

>From my experience with Gump I have to agree with Jan, building is I/O
bound most of the time.  If you add parallelism here, it is likely going
to slow things down rather than speed them up when two javac tasks
compete for the disk.

Having said that there are things in your build that eat up time but are
not I/O-bound.  Running tests for example.

In general Ant cannot know which parts of your build are good candidates
to be spread accross cores and which it shouldn't run in parallel, I
think an explicit <parallel> is better in this case.  Or the tasks would
need to provide options, the <junit> task could provide an option to run
tests in parallel for example.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message