Jeff Dever responded: > There is no need to modify the classpath. You should take the supplied > build.properties.sample and copy that to build.properties. Modify the properties > to point to the ones you have on your hard disk, whereever they may be.
Thanks. I have already done that, and I'm still getting a failed build. Can't find java.net.URLDecoder or setRequestTimeout, get warnings for those, then build failed, then another warning that it can't find the JAKARTA license to copy. Probably something not-quite-right in my build.properties. Hmm. I've commented out the servlet.jar line because I don't have Tomcat or anything else in place yet. (Yeah, I'm lazy. Scrubbed my box a couple of months back, haven't been doing any server-side Java since then.) I've also got the three Anakia properties lines commented out, since I'm not doing anything with xdoc. I had basically the same set of errors with JUnit in my CLASSPATH as I do with JUnit copied into HTTPClient/lib. (Which makes me wonder if the CLASSPATH would work as well as copying the library. I'm probably missing something really obvious. Don't have much experience with Java, much less Jakarta, yet. > Joel Rees wrote: > > > Okay, I admit I'm not looking very hard, but I didn't find this > > mentioned in the archives with a quick search. > > > > When settup HTTPClient up, should I put JUnit in the CLASSPATH or just > > put a copy of the JUnit jar in HTTPClient's lib, like HTTPClient's > > sample build.properties shows? > > > > Feeling like a rank newb, but I'd rather ask than fight error messages I > > don't understand yet. -- Joel Rees <[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
