Sam Ruby wrote:
>
> Daniel Rall wrote:
> >
> > +1 on no build.{sh,bat} files...users should install Ant and use the
> > `ant` command.
>
> For that to work, Ant has to maintain backwards compatibility (which they
> have been pretty good about lately), and projects can't step up to the
> latest features until it has been released.
>
> Peter changed the jar task to accept a "file" attribute, deprecated
> "jarfile", and then proceeded to check in an updated ant.jar into the
> avalon projects.
I agree on this one. Part of build standardization also entails the
build tool being used more like a tool. Once we work through this
piece, there won't be as great a need. Ant has had a stable task structure,
almost everything you need is included. If there is a new feature that
a project absoposolutely (contraction of absolutely and positively--not a
real word) needs a new feature, then they should temporarily have the new
task code in their repository and declare it like any third party taskdef.
> - Sam Ruby
>
> P.S. From personal experience, you can say that nobody should check in Ant
> jars or have build.{sh,bat} files, but people will check them in anyway.
> Even "-1"'s won't stop them. That's why I wrote Gump. I have a single
> build script which can build any project with the collection of jars that I
> specify. The fact that it produces nags that some people find helpful is
> just a fortunate byproduct . ;-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
