First, you need to do the work on a linux or unix system.
Second, like I said, you then need to chmod your way through the directory tree, chaning all the acl's to something appropriate.
Finally, yes, as long as you are running on linux or unix, you can modify your build.xml file to exec the native utility.
Of course, you do have access to such a system--just use your sourceforge account to do the work! Its probably not good to use it as a compile environment, but I don't think anyone will complain if you use it as a release environment. Shouldn't be any problem setting up a cvs client there, though I do recall something in the site docs about having to use different host names, perhaps, when accessing the files under CVS.
One note--if you are seting up a release environment, always use a umask of 0.
Bill
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've cleaned up the acl's in the http zip file.
If anyone is interested, its available at ftp://darklands.cx/pub/qare/httpunit-1.4.zip
Bill la Forge
jxml.com
How did you do it? Did you have to do some post processing? Can the build.xml be changed to make this work?
First, you need to do the work on a linux or unix system.
Second, like I said, you then need to chmod your way through the directory tree, chaning all the acl's to something appropriate.
Finally, yes, as long as you are running on linux or unix, you can modify your build.xml file to exec the native utility.
Of course, you do have access to such a system--just use your sourceforge account to do the work! Its probably not good to use it as a compile environment, but I don't think anyone will complain if you use it as a release environment. Shouldn't be any problem setting up a cvs client there, though I do recall something in the site docs about having to use different host names, perhaps, when accessing the files under CVS.
One note--if you are seting up a release environment, always use a umask of 0.
Bill