FYI JSR 152 is now in PFD
http://jcp.org/aboutJava/communityprocess/review/jsr152/index.html Kevin Jones Developmentor www.develop.com > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Glenn Nielsen > Sent: 25 June 2002 05:34 > To: Tomcat Developers List > Subject: Re: 5.0 proposal > > > Remy Maucherat wrote: > > > > [EMAIL PROTECTED] wrote: > > > It seems we have 3 -1 votes so far. While majority is required, I > > > think we all agree that getting everyone ( reasonable ) > involved and > > > comfortable with the proposal is very important ( and one of the > > > goals of 5.0 ). > > > > +1. > > > > > Christopher: I think we should add your requirement for > performance > > > testing to the proposal. In fact, we should add a whole section > > > about testing for 5.0. Would this satisfy you ? > > > > +1 to start a new commons subproject. > > If everyone else wants to see the bench webapp here, then > I'll remove > > my -1. However, it sounds generic, and not at all dependent > on Tomcat, > > so that's why I think it would be a lot better in the commons. > > > > +1 to add a Tomcat specific performance testing/benchmark repository. > > Perhaps it would be best if it were in its own repository, > jakarta-tomcat-benchmark ? I will help as I have time. > > > > Glenn - I'm not sure what you ask for. The proposal adds no new > > > features (except the new servlet api), and we obviously can't > > > implement the next spec unless it's public. I understand your > > > concern about the time - but given that the code will be shared ( > > > i.e. existing code ) I don't think it should take years to get it > > > done. Is there any particular requirement you want to add to the > > > proposal ? > > > > I added some details about the changes. > > > > > For everyone - the proposal is in CVS, and everyone can > contribute > > > to it. One of the main goals is to improve the community, > and that > > > means we should be more sensitive to other needs. If you have an > > > itch, please add it to the plan, as a goal for 5.0 ( some may not > > > happen in 5.0.0 ). > > > > Not many of the negative comments posted actually contained any > > suggestions, so I didn't see much worth integrating, except Glenn's > > comments about lack of detail. > > > > The latest Tomcat 5 proposal looks much better. I am still > -1 for starting the work until the JCP releases JSR 152 and > JSR 154 for public review. > > There is one addition to the proposal I think we should > discuss at this time. That is the organization of the CVS > repostories for Tomcat. > > The trend started a while ago was to break out common > components into their own repository. > jakarta-tomcat-connectors and jakarta-tomcat-jasper for example. > > Perhaps this would be the time to consider if there are > better ways to organize the code. The reorganization would > have three goals: > > 1. Allow sharing of components between different versions of Tomcat > > 2. Reduce duplication and maintenance of code in multiple branches of > one CVS repository. > > 3. Make the code base in each repository more tightly focused on > what it does, thus making it easier for developers to find bugs > and submit patches. > > As an example, there are now at least 4 different versions of > jasper in various repositories. > > jakarta-tomcat-jasper/jasper34 > jakarta-tomcat-jasper/jasper2 > jakarta-tomcat/jasper > jakarta-tomcat-4.0/jasper > > Tomcat 5 would add a fifth. > > There are many other things that would be in common between > Tomcat 4 and Tomcat 5 which are not dependent on the Servlet > or JSP version. Moving these out of the core Tomcat CVS > repositories would make life easier. > > Thoughts? > > > Regards, > > Glenn > > -- > To unsubscribe, e-mail: > <mailto:tomcat-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
