>>> The only problem I see, is NOT discussing MinTC issues on >tomcat-dev -
>I wholeheartedly agree with this. MinTC issues are not discussed around >here, while I would love to follow its development (darn, not >enough time?). MinTC is an excellent idea but since it's not an Apache project, should it be discussed (more) here ? Solution could be : - host MinTC in SF. - add MinTC as a tomcat 4 subproject and host here in Apache >Actually, I do care _more_ about MinTC than even Tomcat >itself, as the "new >features" of 4.0 (and 4.next) are really something I could care less. Having MinTC included in TC 4.x could help add a new target to TC 4, the embedded market. Did there is a reason against adding it to CVS if Christopher agree. It will be in sync with HEAD, use gump, give ideas which could make a better TC 4.1 or 5.0.... >On this same thread, I don't see many issues related to Tomcat itself >discussed on this list (sometimes I do post about some, but it _really_ >looks like that my posts are redirected to /dev/null - for >instance, see my >post about extension-case matching on MacOS/X... NOONE >replied, not even >cared to ask "Since you run OS/X everywhere, can you find a >fix" or some >things like that. Do you remember what you say yesterday about platform problems ?) >> I will veto this (or vote against, if it's a majority vote). >It has been >> very clear for a while that the Tomcat project has to >provide one and only >> one servlet container for a particular version of the specifications. Yes, and now that TC 3.3 and 4.0 people share effort, jasper/connector, it will be better to see something like MinTC included in maybe it's own tomcat subproject, the goal a minimalistic 2.3/1.2 servlet implementation using TC 4.x .... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
