xmldb

[Antoine Lévy-Lambert <an...@antbuild.com>]

A lot of builds on lsd.student.utwente.nl are failing due to xmldb not 
being there.

The list of full project dependees of xmldb is impressive.

http://lsd.student.utwente.nl/gump/xml-xindice/xmldb_details.html#Full+Project+Dependees

Would it be a good idea to do a fresh build of xmldb on his machine and 
put the jars at one place where the managers of the various gump 
instances can download them from ?

And change the descriptor of xmldb to give the date of the new build to 
the jars ?


Antoine

Re: xmldb

["Adam R. B. Jack" <aj...@trysybase.com>]

> Would it be a good idea to do a fresh build of xmldb on his machine and
> put the jars at one place where the managers of the various gump
> instances can download them from ?
>
> And change the descriptor of xmldb to give the date of the new build to
> the jars ?

Looks like Stefan has updated the xmldb descriptor (in xml-xindice) to
reference the correct jar names.

Two things:

1) We need a new term for projects that aren't pakcages, but aren't built by
Gump. XMLDB is one such, it has it's jars with it in CVS, (so all Gump
instances do get them). I annotate a project as prebuilt (see the first Note
on http://lsd.student.utwente.nl/gump/xml-xindice/xmldb.html). I think
'Prebuilt' is a fine term. Prebuilts are downloaded from CVS ('cos licensing
allows) whereas Packages have to be administrator installed.

I need to add a TODO to list the Prebuilts like we list the Packages:
http://lsd.student.utwente.nl/gump/packages.html. Also, somehow we need to
visualy annotate them differently.

2) I put a (not sure if it is worth much) 'metadata location' -> project
xref page, so we can look at where metadata resides. I probably ought add
'metadata location' on project page.

regards,

Adam