Now I do have a development environment for HttpClient. It was less troublesome than I was afraid of, but the result is shaky. I got the IBM JDK 1.3.1 running after patching the startup skript, and the Blackdown 1.2.2 after compiling and pre-loading the internal procedure that is no longer in glibc.
One problem is that I can compile HttpClient with either JDK, although I did *not* install JSSE and JCE. That may have to do with the fact that I'm using the Ant tool that comes as part of my Linux installation, and that tool always starts itself with the system JVM which is at version 5.0. I noticed strange behavior in HttpComponents too, when I could compile HttpClient although I didn't have the commons-logging.jar configured in the build file. Some things seem to get picked up from the Ant classpath. Another problem with my HttpClient environment is that "ant clean compile test" reports errors. Two when using BD122, between 0 and 3 when using IBM131. If I run the tests in a separate call: ant clean compile ant test then no errors are reported with either JDK. All in all I believe the environment is just good enough to create patches, but somebody else will have to test them in a proper environment. In the long run, I will have to manually set up two separate Ant installations that do not use the system JVM, one for HttpComponents and an older one compatible with Java 1.2.2 for HttpClient. Write Once, Test Anywhere... cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
