> Remy Maucherat at [EMAIL PROTECTED] wrote: > > > Do it, even if that would make the build process (even) more > > complex. > > I believe this can be achieved by simply copying the few interfaces over to > jakarta-tomcat-4.0. Once those have been defined, they shouldn't change. > While the actual big work is on the C code, which is the real thing we want > to develop... And that part is completely separated from Tomcat, and its > build process... Ok. +1 then. Remy
- Re: Separating Service code ... Pier P. Fumagalli
- Re: Separating Service code ... Pier P. Fumagalli
- Re: Separating Service code ... Remy Maucherat
- Re: Separating Service code ... jean-frederic clere
- Re: Separating Service code ... Pier P. Fumagalli
- Re: Separating Service code ... Andy Armstrong
- Re: Separating Service code from Tomcat 4.0 jean-frederic clere
- Re: Separating Service code from Tomcat 4.0 Mike Anderson
- Re: Separating Service code from Tomcat 4.0 Remy Maucherat
- Re: Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- Re: Separating Service code from Tomcat 4... Remy Maucherat
- Re: Separating Service code from Tomcat 4.0 cmanolache
- Re: Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- RE: Separating Service code from Tomcat 4.0 GOMEZ Henri
- Re: Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- Re: Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- RE: Separating Service code from Tomcat 4.0 Kevin Seguin
- Re: Separating Service code from Tomcat 4.0 Pier P. Fumagalli
- Re: Separating Service code from Tomcat 4.0 Joe Flowers
- Re: Separating Service code from Tomcat 4... Remy Maucherat
- Different approach to TC as a service (wa... Andy Armstrong