Hi Sam, I have a first, very rudimentary auto jar downloader working from the version deps in the project descriptors.
Could we discuss the layout of the jars you produce in the nightly builds? Could we move toward something that could be used by the auto build system so that people can use released versions and the latest nightlies if they wish. I was thinking that the main JAR archive could be listed by project so the auto downloader can find them a little easier. Possibly just a different view of what you have now using symlinks. Then within the project directory either directories for the different versions if we are going to keep version numbers out of the jars, or we can put the jars all in the same directory if we are going to use version numbers. Basically I would like to combine what's available under http://jakarta.apache.org/builds/ with what Gump produces night to create a unified JAR archive. Then do you think we could figure out a schedule and strategy for distributing the archive to a number of machines. Maybe the same mirroring strategy used for the apache http products? I'm keep to keep working on the auto downloader and builder. So far only 4-5 people have tried to build stratum and they have all been successful. I added simple proxy support so a user behind a firewall also built stratum successfully. I am now very excited! :-) -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
