Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 51682 invoked from network); 4 Feb 2003 00:16:21 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 4 Feb 2003 00:16:21 -0000 Received: (qmail 12478 invoked by uid 97); 4 Feb 2003 00:17:55 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@nagoya.betaversion.org Received: (qmail 12471 invoked from network); 4 Feb 2003 00:17:55 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 4 Feb 2003 00:17:55 -0000 Received: (qmail 50774 invoked by uid 500); 4 Feb 2003 00:16:09 -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 50763 invoked from network); 4 Feb 2003 00:16:09 -0000 Received: from nwkea-mail-2.sun.com (192.18.42.14) by daedalus.apache.org with SMTP; 4 Feb 2003 00:16:09 -0000 Received: from ha1sca-mail1.SFBay.Sun.COM ([129.145.155.51]) by nwkea-mail-2.sun.com (8.9.3+Sun/8.9.3) with ESMTP id QAA13215 for ; Mon, 3 Feb 2003 16:16:16 -0800 (PST) Received: from laguna (laguna [129.145.166.120]) by ha1sca-mail1.SFBay.Sun.COM (8.11.6+Sun/8.10.2/ENSMAIL,v2.1p1) with SMTP id h140GEh02241 for ; Mon, 3 Feb 2003 16:16:14 -0800 (PST) Message-Id: <200302040016.h140GEh02241@ha1sca-mail1.SFBay.Sun.COM> Date: Mon, 3 Feb 2003 16:16:14 -0800 (PST) From: Jan Luehe Reply-To: Jan Luehe Subject: Re: JSP API javadocs out-of-date To: tomcat-dev@jakarta.apache.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: N/1RheUMgxNIkyWDQaNAfw== X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Remy, > Jan Luehe wrote: > > I've noticed the JSP API javadocs at > > > > http://jakarta.apache.org/tomcat/tomcat-5.0-doc/jspapi > > > > are out-of-date, and I'm wondering what I need to do in order to sync > > them up with the latest API versions at jakarta-servletapi-5. > > > > The JSP API javadocs in the nightly build of the tomcat-docs webapp > > are up-to-date. > > > > Any suggestions? > > The online docs are synced with the latest release from the branch. So > since no releases were made since 5.0.0 (for whatever reason), it was > not synced up. > > I'd like to keep this syncing. would you consider removing the link to the online API docs while the APIs are not final? This would give people an incentive to check the API docs link in the nightly build, which is always up-to-date. Otherwise, people are likely to get confused if they see APIs that are out-of-date. Thanks, Jan --------------------------------------------------------------------- To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org