You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by ru...@us.ibm.com on 2000/06/24 06:04:02 UTC

RE: nightly build (was: problem)


Conor MacNeill wrote:
> Actually ant is built nightly under the tomcat area
>
> http://jakarta.apache.org/builds/tomcat/nightly/
>
> Perhaps ant should have its own nightly build process. An added
> benefit would be to allow tomcat to fix on a particular ant version.

Since this is an all volunteer organization, everyone is empowered to set
one up themselves and publish it.

One difference of opinion I have with the nightly build process mentioned
above is that it fixes on a particular ant version for the nightly build
itself.

I have started my own nightly build, which bootstraps ant from source and
incidentally compiles a few (<grin>) other projects using the version of
ant just built - purely as a regression test of Ant, of course.  ;-)

I mentioned it here before, but if you want to see the rationalle, current
script, logs, and results, visit:

   http://oss.software.ibm.com/developerworks/opensource/jakarta/nightly.html

- Sam Ruby



RE: nightly build (was: problem)

Posted by Conor MacNeill <co...@m64.com>.
> -----Original Message-----
> From: rubys@us.ibm.com [mailto:rubys@us.ibm.com]
>
> Since this is an all volunteer organization, everyone is empowered to set
> one up themselves and publish it.

OK, but most people looking for an updated build of ant come to
jakarta.apache.org. They may not realise that ant is to be found under
"Tomcat and Other subprojects". Certainly a number of posts here indicate
that people are using the ant build that is part of Tomcat 3.1 (modern
compile problems, etc). Is there a process for changing the nightly builds
done on jakarta.apache.org?

>
> One difference of opinion I have with the nightly build process mentioned
> above is that it fixes on a particular ant version for the nightly build
> itself.

It is cool to bootstrap ant itself for its nightly build. I don't know if it
is necessary, however, to build all other projects with the latest version
of ant. This couples all the projects together. Say we change ant to
eliminate the ${} property syntax - we need to move all the other components
to this new version of ant to restore the nightly builds. It puts the onus
on ant to make sure all other projects still work when changes are made to
ant. It may be better to let other projects fix on a version of ant and then
decide when they want to upgrade to a later version.

Conor