Links Docs Home User Guide 1) Introduction 2) Setup 3) First webapp 4) Deployer 5) Manager 6) Realms and AAA 7) Security Manager 8) JNDI Resources 9) JDBC DataSources 10) Classloading 11) JSPs 12) SSL 13) SSI 14) CGI 15) Proxy Support 16) MBean Descriptor 17) Default Servlet 18) Clustering 19) Load Balancer Reference Release Notes Tomcat Configuration JK Documentation Servlet API Javadocs JSP API Javadocs Tomcat Development Building Changelog Status Developers Functional Specs. Tomcat Javadocs Jasper Javadocs Architecture |
# The Apache Jakarta Tomcat 5 Servlet/JSP Container ## Project Status | print-friendly version
Preface
This document attempts to convey the current status of Tomcat development in "big picture" terms. This is not the place to check if an individual bug report has been addressed or when an individual feature will be available. This page is updated roughly once per every couple of Tomcat minor releases, so for day-to-day status you should check the tomcat-user and tomcat-dev mailing lists. You can always inquire there as to the availability or status of a specific feature or component.
Current Status Summary
Tomcat 5.0.27 was released on June 17th, 2004. At that time, the TOMCAT_5_0 branch was tagged in CVS, and work on Tomcat 5.1 (or 5.5, or 5.next, we haven't decided yet) began. Until the first stable release of Tomcat 5.1, building from CVS head may be unstable or broken: use the TOMCAT_5_0 branch tag to build the Tomcat 5.0 releases. Tomcat 5.1 has several major goals. They are discussed in the tomcat-dev mailing list's "5.next" thread: MARC. The status of some of these items is detailed below. Tomcat 4.0.x is relatively old, and not actively maintained or supported. It is strongly recommended that users of these releases upgrade to the latest stable Tomcat 5.0 release or at least the latest stable Tomcat 4.1 release. Tomcat 4.1.x is no longer actively developed. It is maintained to address only showstopper, security, and Servlet Specification compliance issues. Maintenance for Tomcat 4.1.x will likely cease once a stable release or two of Tomcat 5.1 are out. Users of Tomcat 4.1.x are strongly encouraged to upgrade to the latest stable Tomcat 5.0 release. Tomcat 3.3.x is in roughly the same maintenance mode as Tomcat 4.1.x. Tomcat 3.2 and earlier are in roughly the same support state as Tomcat 4.0.x. Users should upgrade to Tomcat 3.3.x or the latest stable Tomcat 5.0.x.
How to read the report
The columns in this report contain the following information: Priority - A sense of how important it is to address this issue in the short term. Action Item - Concise description of the action item to be completed. Where relevant, Java package names of the primary classes involved are listed in [square brackets] Volunteers - Login of those developers who have volunteered to assist in the design, implementation, testing, and documentation of this action item's changes to Tomcat. Developers can nominate themselves to work on particular action items by asking a Committer to add their name address to those items. The developers working on each item should discuss and agree upon the approach to be used for implementing the item's changes to the project source code and documentation, prior to completing those changes. Such discussions should take place on the tomcat-dev mailing list so that everyone can stay apprised of what is going on, or chime in if they want to contribute ideas and suggestions.
TODO List
> Priority | Action Item | Volunteers
> --- | --- | ---
> High | Refactor ClassLoaders for Tomcat 5.1. | remm, costin
> High | Refactor application deployment for Tomcat 5.1. | remm
> High | Remove Logger interface and implementation, use commons-logging everywhere. | remm
> Medium | Enhance Cluster functionality for Tomcat 5.1. | fhanik
> Low | Update docs, site, and FAQ for Tomcat 5.1 once ready. | yoavs, funkman
> Low | Continue fixing bugs ;) | everyone

Open bugs
The list of the bugs which are in an unresolved state for Tomcat 5 can be seen here. Aspiring volunteers and others are strongly encouraged to attempt to comment and help resolve these issues.

Copyright © 1999-2003, Apache Software Foundation