+1 The plan ( after I finish native2 ) is to try using the 4.0/3.3 connector code from Coyote for jk2 ( the java side ), so this will not be duplicated.
Costin On Tue, 26 Mar 2002, GOMEZ Henri wrote: > Now that there is a build dir for jtc I'd like to populate > it with a bunch of rpm and linux binaries for mod_jk > (mod_webapp still need some works) with/without eapi > > there is allready there a coyote dir > > /coyote/release/v1.0-b1/ > /coyote/release/v1.0-b2/ > /coyote/release/v1.0-b3/ > /coyote/release/v1.0-b4/ > > what about also : > > /jk/release/v1.0-b1/ > /jk/release/v1.0-b2/ > > where we could mimic the tc 3.3 tree : > > KEYS 05-Mar-2002 04:42 5.9K > bin/ 05-Mar-2002 04:42 - > rpms/ 05-Mar-2002 04:42 - > src/ 05-Mar-2002 04:42 > > bin : > > linux/ 05-Mar-2002 04:42 - > netware/ 05-Mar-2002 04:42 - > win32/ > > > The idea will be to have regular snapshot from jtc and > put there the source tarball and binaries : > > - mod_jk > > - native=jk 1.2 for Apache 1.3/2.0/IIS/iPlanet > - native2=jk 2.0 for Apache 1.3/2.0 > > - java libs > > - jkant, tomcat-utils > > > BTW, it should be nice to have also in coyote release a source tarball > of jtc ;) > > It will help users find somewhere the up to date binaries for > connectors, and remove that kind of stuff from tomcat 3.3/4.0 > subdirs... > > Thanks to comment ;) > > -- > 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]>
