ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: Release log file lock from <record>
Date Thu, 02 Dec 2004 09:10:20 GMT
On Thu, 2 Dec 2004, Robert Soesemann <rsoesemann@sapient.com> wrote:

> I tried out exchanging my ant.jar with the one from
> /~bodewig/builds/ant/20041126 and it works perfectly!  How
> stable/buggy is this version?

Successfully builds performs a few hundred builds of Jakarta and other
Java projects every few hours
<http://brutus.apache.org/gump/public/buildLog.html> ;-)

Quite general I'd say that the "old" tasks are at least as stable as
the released ones while new stuff (the repository tasks Steve is
working on, for example) are more unstable - both their API and their
behavior.

Of course there are potential problems if changes happen on major
parts, like when I'm going to commit my modified DirectoryScanner
tomorrow, which has the potential to break all tasks using FileSets.

Personally I use Ant's CVS HEAD in production all the time, but I also
have the privilege to fix problems I encounter immediately.  I
couldn't do .NET development with Ant 1.6.2 (since I use Mono), for
example.  My co-workers share the joy and pain of CVS HEAD.  Most of
the time it works extremely well, but sometimes things break and heads
turn towards the local Ant guru (for some reason that's me).

> Could it be a problem to just exchange the ant.jar and not the whole
> package?

Asked that way, the answer must be "yes".  It is always possible that
we've changed some internal contracts that tasks from one of the
optional packages need to know about.  I don't remember such a change
from the top of my head, but that doesn't mean it hasn't happened.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org


Mime
View raw message