Copying alexandria-dev.
Others can run builds with stable dependencies. They are permitted, and
even encouraged to do so using Gump. The runs I have been making are to
determine the impact of changes - something that I think that has not
received enough attention, and so that's why I have been and will continue
to focus the runs that I make on that.
Since you gave the specific example of ant, I do not like the idea of
ant-1.3 being released without some assessment of the impact of changes on
other projects. There was a change that would have gone into 1.3 that
would have caused xerces and xalan packaging builds to fail, this was
changed to a way that would still cause it to fail, but in order to change
it to make is succeed would have required developers to step up to 1.3, and
finally, a change was made that did not require any changes.
Given the number of projects we have here, each project binding too closely
to exactly one version of each of their prereqs means that someone who
desires to compose a system out of these components is likely to run into
problems. So, in fact, I would be greatly pleased if there were multiple
nightly builds going on out there with different combinations. And
alexandria can certainly house the various project definitions required,
and
Making ant build.xml files as a target of gump would be a valuable
addition. It has been often discussed, but never contributed.
Getting using http as an alternative to cvs would also make a great
addition.
- Sam Ruby
P.S. What does it mean to have gump "working", but not
"updating/building"?
---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 02/15/2001
03:18 PM ---------------------------
[EMAIL PROTECTED] on 02/15/2001 03:07:04 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Nightly builds
Hi Sam,
I (think ) I got gump to work, it's not updating/building. There are few
issues/sugestions. I tried to find the alexandria list ( I assume the
discussion on gump happens on alexandria ), I'm sure it is somewhere and
I'll keep searching :-)
Anyway - it would be possible to switch tomcat3.x nightly builds to use
gump, with few small changes in the project definition.
The main issue is that (IMHO) you should relax a bit the
dependencies: a number of projects had releases, and I think other
projects should depend on the (stable) release of those projects.
For example, tomcat, servletapi, etc should depend on released-ant-1.2,
not jakarta-ant, etc.
Whenever a project has a major release - we should of course update the
scripts to make all projects depend on the latest "stable" and fix all
projects that are in development mode to match the latest "stable".
Given that each project has independent release cycle, I don't think it's
normal for a stable release of a project to depend on a development
release of another project ( for example, tomcat 3.3 shouldn't depend on
the dev. release of ant - but on the latest "stable" ant. If ant1.3 will
be released before 3.3 is "frozen", then tomcat3.3 should be fixed to
make sure it works with ant 1.3 - if not, it should stay dependent on
the released ant 1.2 ).
This can be resolved by adding "project/released-ant-12.xml", etc.
Another issue - wouldn't be better to generate build.xml instead of
build.sh and build.bat ? Most of the code inside build.sh can be done
easily in a "super" build.xml that calls ant. It is even possible to
use <java> tags to start different VMs.
I think this would be easier to maintain and enhance.
Another think - one planned feature for tc3.x build was a mechanism to
triger a build from a web page ( so if someone does a change, he doesn't
have to wait until the next night to find out if it brakes something ).
My plan was to use the <ant> taglib ( that is also used to run the tests
from a web page ) and write a simple build.war that will allow runs of
the build from the web.
That would also allow a lot of simplification ( since wars are
self contained and have a stable environment/structure ). It would also
modularize a bit the build ( a page to update a repository, a page to
build, no more "echo \<foo\>", etc )
Finally: it would be nice if the build scripts would get the sources using
<http-get> instead of <cvs>.
Costin
---------------------------------------------------------------------
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]
