You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by co...@apache.org on 2001/02/27 18:43:21 UTC
cvs commit: jakarta-tomcat/apps README
costin 01/02/27 09:43:21
Added: modules README
apps README
Log:
Added the top-level directories for the contributed modules and
apps that will not be included in the release ( either because
they are not ready or as a choice to keep the release focused).
This will allow us to check in the new adminUI and the digested auth.
Modules here should be considered "revolution"-like, and are not part
of the release ( or optional/ in ant terms ).
The main goals are to avoid featurism in the released tomcat, while
allowing people to add the functionality they need ( without impacting
the release cycle )
Revision Changes Path
1.1 jakarta-tomcat/modules/README
Index: README
===================================================================
This directory is for various modules that are not part of the
normal tomcat release.
The goal is to keep the tomcat release as small and focused as
possible, and include only the stable modules, but still allow
users to add or try other modules..
Examples:
- different authentication schemes ( the "digested" auth, LDAP, etc )
- different loggers ( log4j, etc )
- session persistence
- ajp14
- etc.
Each module can be build independently, and will act as an add-on
for the stable release of tomcat. Tomcat can remain focused to a
strict and minimal implementation of the API, and all specialized
modules can be developed without impacting the release cycle.
Note: some of the existing modules in tomcat fit in this category.
We can move them here only with a vote on tomcat-dev, since they
were part of previous releases.
1.1 jakarta-tomcat/apps/README
Index: README
===================================================================
Various applications that are not required for normal
tomcat functionality, but provide additional support.
The new contributed admin pages, and new apps ( like config or
monitoring ) should be developed here, independent of
the main tomcat release. When the app is stable and
have the same quality with the rest of tomcat we can
vote to include it in the stable release, but as
the development is active the apps can be built and
released separately.