+1 for separate repository, but I preffer 

"jakarta-tomcat-modules" or some common repository.

Reason: connector and jasper are just particular modules that could be
used in multiple versions of tomcat ( like 3.2, 3.3, 4.0 or 4.1 ). There
are other pieces that could be developed in the common repository.

If you want, we can have all 3 ( connectors, jasper, modules ) - but I
would really want a repository to replace the current /proposal and be
usable in multiple tomcat versions. 

For example the JAAS auth, the logger ( that would be really needed in
3.2 for example ), and maybe even the build tool.

Costin


> Over the last few weeks, there has been a lot of discussion on
> collaborative development, across the various Tomcat branches, on two
> major areas:
> 
> * Web connectors
> 
> * A new Jasper (the "jasper34" proposal)
> 
> and efforts have begun in the HEAD branch "proposals" directory of the
> jakarta-tomcat repository.  I'd like to propose a slightly different
> approach -- create two new repositories (perhaps
> "jakarta-tomcat-connectors" and "jakarta-tomcat-jasper") to be the homes
> of these development efforts, independent of any of the existing code
> bases.  The reasoning for this approach is as follows:
> 
> * Avoid any appearance of politics or attachment based
>   on which repository the code is hosted in
> 
> * Make it easier to enforce the technical separation of
>   this code from any existing Tomcat base code (you have
>   to declare external dependencies pretty directly)
> 
> * Avoid the need for everyone working on these shared
>   components to have *all* of the Tomcat code on all branches
>   checked out all the time -- you can focus on the repository
>   for your favorite Tomcat plus the common stuff you care about
> 
> * Smaller CVS repositories means faster CVS checkouts for everyone
>   on daedalus, on all projects
> 
> Because these repositories would both be part of the overall Tomcat
> subproject, all existing and new Tomcat committers would have commit
> access to both of them, just as we all have access to "jakarta-tomcat" and
> "jakarta-tomcat-4.0" today.
> 
> Comments?  Questions?  Votes?
> 
> Craig McClanahan
> 

Reply via email to