Berin Loritsch [mailto:[EMAIL PROTECTED]] wrote:
> The current trend among Jakarta projects is to require developers to
> install ant on
> their machines locally--and be responsible for current updates. The
> reason is that
> it is becomming increasingly clear that we would otherwise have an
> installation
> for EACH repository we have checked out. This was true of all the
> Avalon projects
> until we unified their build systems.
>
The problem I see is that new versions of Ant can (and have) introduced
various incompatibilities with prior versions. This means that all projects
have to ensure that they are all using the same version of Ant and that they
all upgrade their build projects and make a new release at the same time
when a new build of Ant is available. (Or require developers to screw with
switching back and forth between different Ant versions manually every time
they want to build a different project).
> This approach has its merits and drawbacks. The merits are that it
> raises interest
> in Ant, and possibly contributing to Ant. Drawbacks include
> the loss of
> simply typing
> ./build.sh to get the build going. (Actually, we can keep the build
> scripts that will simply
> run the installed Ant).
>
If I had a vote, I'd vote -1 (for the reasons indicated). Hard drive space
is cheap. My time is not. :)
- Sean T.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
