I'm trying to make a rpm for it but I'm stuck with chicken-eggs problems between TC 4.1.0 and JTC (ditto for latest TC 4.0.4 and JTC).
To follow rpm policies I should avoid using pre-built binaries (like commons-logging, coyote, http11....). And coyote/http11/jk need tomcat 4 to be built ! I'll have to try some kind of bootstrap action in my rpm, start compiling TC 4.x with binaries, then goes to JTC and rebuild it against newly built TC 4.x, then install these in place of bundled binaries ?(8 - Henri Gomez ___[_]____ EMAIL : [EMAIL PROTECTED] (. .) PGP KEY : 697ECEDD ...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-----Original Message----- >From: Remy Maucherat [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 30, 2002 11:50 AM >To: Tomcat Developers List >Subject: [4.1.0] Anyone testing it ? > > >Is anyone testing 4.1.0 ? >The URL as a reminder: >http://jakarta.apache.org/builds/jakarta-tomcat-4.0/test/v4.1.0/ > >Obviously, I expect people voting to rate the build to have >tried it ;-) > >Of particular interest is testing: >- AJP 1.3 support >- To see if bug 5735 is fixed with the current Coyote connector >- Jasper 2 > >Thanks, >Remy > > >-- >To unsubscribe, e-mail: ><mailto:[EMAIL PROTECTED]> >For additional commands, e-mail: ><mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
