Hey jason, What do you think of the idea of server controlled versioning. In other words, instead of putting the version numbers of the .jar files in deps.list, the system would instead connect to the server (jakarta.apache.org) and get the version numbers.
This way, all you have to do is list the dependencies and you never have to worry about updating a bazillion deps.list files every time a new version of the software comes out (you simply update it on the server). When you run update-jar's, it will download the correct versions of the files based on the version number that update-jar's sends to the server. One could also do cool things like have it be that if someone is building a project from cvs head (and update-jar's sends a -dev version number), then update-jar's would download the jar files which were built from gump the night before (or something like that)... The idea is to still keep the dependencies locally defined, but keep the versioning centrally defined. Makes for less maintenance. -jon -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
