Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@www.apache.org Received: (qmail 39344 invoked from network); 17 Dec 2003 18:01:07 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 17 Dec 2003 18:01:07 -0000 Received: (qmail 5956 invoked by uid 500); 17 Dec 2003 18:00:37 -0000 Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 5885 invoked by uid 500); 17 Dec 2003 18:00:37 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 5831 invoked from network); 17 Dec 2003 18:00:37 -0000 Received: from unknown (HELO prv-mail20.provo.novell.com) (137.65.81.122) by daedalus.apache.org with SMTP; 17 Dec 2003 18:00:37 -0000 Received: from INET-PRV-MTA by prv-mail20.provo.novell.com with Novell_GroupWise; Wed, 17 Dec 2003 11:00:40 -0700 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.2 Beta Date: Wed, 17 Dec 2003 11:00:29 -0700 From: "Jeff Tulley" To: Subject: Re: Understanding jakarta-tomcat-4.0 cvs source base / jasper Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Kin-man, Thank you, that is exactly the answer I was looking for. That makes things a lot more clear. I would suggest removing the j-t-4.0/jasper directory then, since 4.0.x seems done with. >The source for Jasper in Tomcat 4.1.29 is from j-t-j/jasper2 with >Tomcat_4_branch tag. The head branch is for Tomcat 5. >A lot of bugs filed against Tomcat 4.1.x has been fixed in Tomcat 5. >Unfortunately I don't have cycles to apply the fixes to 4.1.x. It would >be great if someone can do that, and I can help and/or anser questions if >needed. >The branch jakarta-tomcat-4.0/jasper was used for Tomcat 4.0.x releases, >and I don't think we are making new releases for Tomcat 4.0.x. >-Kin-man >> Quick question - Does the jasper that ships with Tomcat 4.1.29 come from >> the source code in jakarta-tomcat-4.0/jasper, or is it from the >> jakarta-tomcat-jasper CVS module? > >> I am looking at some bugs in Bugzilla against Jasper, where they >> complain about something in j-t-4.0/jasper/src/(some class), and the bug >> is fixed in j-t-j/jasper2/src I do not know whether to mark the bug as >> fixed or investigate further. >> >> If the answer turns out that the source code in j-t-4/jasper is NOT >> being used, what is there against removing it to avoid confusion? Jeff Tulley (jtulley@novell.com) (801)861-5322 Novell, Inc., The Leading Provider of Net Business Solutions http://www.novell.com --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org