> Do you all have accounts on jakarta.apache.org? I don't, AFAIK. I asked [EMAIL PROTECTED] to get one, but got no answer.
Having the docs in CVS makes it convenient, because all you need to do is log in to jakarta.apache.org, cd to the right directory, and type "cvs update -d", and you're done publishing the docs. I would not want to have to scp a tarball and unzip it there - that's a pain. It's bad enough I have to do that to make a release. If I had to do that everytime I updated the web site, it wouldn't get updated very often.With the proper setup, it can be a 1-word command -- and actually quicker than a cvs co... I'd take care of scripting it if we finally chose this option.
I don't see a problem with the docs in CVS. But then, I use WinCVS, which is very handy and quicker than using command-line cvs. I could hardly "miss" or forget to update the docs, because WinCVS makes it obvious when I have modified files that I haven't checked in.Me too with lincvs, but what about people using command line (is there any?).
> I'm also wary of pulling JUnit from the distribution. How sure are you this won't be
> a problem? Have you tested all of JMeter's functionality without it?
No, I haven't. Anyway, JUnit is still there for the time being -- just not the one used by Gump for the compile, but the one we have on CVS. It's a long story... to make it short: these Gump nightly builds are strange creatures: they are built from the latest code from CVS for each package. I need to replace the .jars in jakarta-jmeter/lib to ensure they run with the same versions they were compiled with.
Do you think it's any likely that it will break anything? Doesn't look like to me... should be used only at test-time, shouldn't it?
Salut,
Jordi.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
