Bertrand Delacretaz wrote: > On Dec 5, 2007 12:06 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > >> ...what about using 2.5 everywhere but try to be >> 2.4 compatible?... > > How do we check the "2.4 compatible" bit if using the 2.5 APIs? > > That sounds like a hard promise to keep, and I'd hate having us waste > time helping users fight with servlet engine compatibility problems. > Hmm, in general I agree with you, but :) I don't think that this is a very big effort - for example we did this in Cocoon for years. Now, if we implement the 2.5 version whereever we implement servlet api things ourselves (like our own servlet context impl in core) and use 2.4 version everywhere else this should work fine.
Rereading my email, I was a little bit unclear :) I think we should use the 2.4 version in most of our poms, so we can assure that only 2.4 api is used. However if we implement servlet api somewhere, this module should use the 2.5 version (if I see this correctly this is currently just core and api). Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
