The automated Gump builds seem to be working OK on Covalent and Nagoya: http://gump.covalent.net/log/jakarta-jmeter.html http://nagoya.apache.org/~rubys/gump/jakarta-jmeter.html
But the "main" builds on CVS are still not working: http://cvs.apache.org/builds/gump/latest/ This which means that the "Nightly tarball" link on the JMeter home page: http://cvs.apache.org/builds/jakarta-jmeter/nightly/ points to builds which are rather out of date. I've just updated the JMeter Gump project file to save the nightly build source and binaries as Zip files on Covalent.These should be visible from tomorrow at: http://gump.covalent.net/jars/latest/jakarta-jmeter/ It's easy enough to save the TGZ files instead of - or as well as - the Zip versions. I figured Windows users might have more problems with the TGZ format, than Unix users would with ZIP... The 3rd-party libraries are not saved there: - I was not sure about licence issues - they don't change nearly as often - easy enough to fetch them from CVS (or even the other directories on covalent) If Gump on cvs.apache.org is not fixed soon, perhaps the Nightly tarball link on the JMeter home page should be changed to point to the covalent directory. By the way, it seems that Gump updates its copies of the source from CVS a long while before the actual build, so it can take a day or so for changes to filter through. [It looks like Gump does all the CVS updates first, and then all the builds.] -- S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
