I do agree with Martin that if we do this, we should really use subversion. I know that we are not ready for subversion yet so maybe that means we should hold off.
I think there might be some advantages to the subproject idea but IMO we have a lot of other basic stuff to get under control before we contemplate any major changes. We still have a lot of other important items on the table: documentation, mailing list change, additional material for the website, nightly builds, upcoming release, etc. Keep in mind that Struts has a *much* bigger user base and a lot more committers. Also they switched to Subversion for just this reason. The Struts team has people committing 24/7 and they are probably better equipped to handle a bunch of subprojects than we are right now. My .02 sean On Tue, 15 Mar 2005 13:25:50 +0100, Manfred Geiler <[EMAIL PROTECTED]> wrote: > Sylvain Vieujot schrieb: > > Right now, I use the all in one jar, that also contains the javax.* > > namespace, and I have no problem (tomcat 5.5). > > Are you sure about this need to separate those classes ? > > I do not know for tomcat 5.5, but with tomcat 5.0.x I had serious > problems when I deployed more than one webapps in different contexts and > every app had it's own javax.faces.* classes. Putting the > myfaces-api.jar to /common/lib solved this problem and is also the right > place as far as I understand the Tomcat structure. > > Manfred > > > > > > Thanks, > > > > Sylvain. > > > > On Tue, 2005-03-15 at 09:58 +0100, Manfred Geiler wrote: > > > >> But keep in mind that the JSR-127 API always must be > >> separated because of the javax.* namespace that is handled specially by > >> container classloaders. For Tomcat JSR-127 API should be in /common/lib > >> for instance. > > >
