OK, that'd be easier. :) I'll give it a try. Thanks for the suggestion.
> Date: Wed, 27 Mar 2002 14:59:00 -0800 (PST) > From: [EMAIL PROTECTED] > Subject: RE: [PLAN] New Jasper > X-X-Sender: <[EMAIL PROTECTED]> > To: Tomcat Developers List <[EMAIL PROTECTED]>, Kin-Man Chung <[EMAIL PROTECTED]> > MIME-version: 1.0 > X-Authentication-warning: dyn-181.sfo.covalent.net: costinm owned process doing -bs > > On Wed, 27 Mar 2002, Kin-Man Chung wrote: > > > I checked out jakarta-tomcat-jasper briefly looked at the files there. > > I agree with you (and constin) that it can be used as a repository for > > jasper2. > > > > However, files and directory structures are too different from the one > > used in tomcat 4, and I am a little hesitant to just go in there and > > wipe out everything, not knowing the current status of that repository, > > or its intended use (tomcat 3, 4, or both?). In the interest of getting > > jasper2 out in reasonable time, I am going to stick with my original plan. > > That'd also give me some time to digest what's in jakarta-tomcat-jasper, > > and see if jasper2 should move in there. > > Just create a jasper2 directory - and don't touch the old one. > > The idea is similar with what's in j-t-c - there are multiple 'projects' > going on, each using its own conventions. > > The structure of jasper3.4 shouldn't affect jasper2, and you don't need > to 'digest' the old code ( any more than we digest each other's work > in connectors ). > > I can't see how creating the directory in j-t-j can affect your timing. > If it's build issue ( build.xml, etc) - it's easy to solve ( Remy > already did most of the work for coyote ) > > costin > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
