OK, after not getting a chance to clean it up and publish this, I am
going to publish it to you guys anyway...

You can get it from http://www.eionline.com/Gump.zip


The files attached should probably rest in antoher proposal for now,
but I wanted to continue using Sam's project definitions.  The only
changes I made were very simple, such as adding a basedir attribute to
the ant tag. When the file was something like build/build.xml, I
changed it to have a basedir of build and a file of build.xml.
Nothing too complicated.

The idea of my implementation is that you start the script via
build.py, and then everything goes from there.  The projects are
merged, and then sorted, no different from Sam's, and then I create
ant files for each and every project, and then run them in the
dependency order.  The files get from CVS, check dependencies, and
then build.  The XSL is a little wacked, but I think I have the major
points in there.  In the master ant file, I actually use the <java/>
tag instead of the <ant/> tag, so that a build failure won't fail the
whole system.  I am also usig Saxon right now, as Saxon is my realm of
knowledge, and I use a few tricks that I haven't boned up on in Xalan
yet, like multiple output files...

The system uses fails to test for succesful building of dependencies,
and ALMOST works.

I got down to adding the dependent jars to the classpath, and that is
where I am currently.  The status html stuff needs a lot of work (it
is barely started), but here it is.

I would like to get this in CVS for all to work on, but I would like
to see this in such a way so as to use Sam's project definitions, and
eventually Alexandria's.  There is no need to have another copy of
those around ;-)

Also, I would like to add the nag stuff to the project definitions
themselves, so the build can fire off an email based on the result.
Any thoughts on that?

I am happy to continue working on this, either here or personally.  I
will let you guys decide.

Thanks
Scott Sanders


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to