Spring 4 and Servlet 3.0

[Tom Zeller]

>>> So the only question that remains before we can make a decision one way or another is whether we can override the dependency in the Spring Framework POMs so that our dependency is explicitly on 2.5, while running our tests with 3.0 provided, and thus retain the ability to deploy with 2.5.
>>
>> To make sure I understand, are you saying that we want to explicitly
>> declare compatibility with Servlet 2.5 to support deployers whose
>> container does not support Servlet 3.x ?
>
> No, I'm really only saying that it *might* be possible to do that, and asking whether we think it is something we want to explore.

I probably would remain neutral to slightly negative regarding
attempting to target a version of the Servlet API other than that
specifically targeted by Jetty, my understanding is that Jetty 9.1
targets Servlet API 3.1, I don't know about Tomcat. The main change in
the Jetty 9.x series, as far as I know, is internal work to support
the new Servlet API NIO, which I do not think is of strategic concern
to us, as discussed previously.

Open to other ideas.