Spring 4 and Servlet 3.0

[Tom Zeller]

> I admit I didn't try the testbed because I was unfamiliar with it.

Kind of an aside, but with our Spring wiring being "ignored" by
Eclipse when looking for references to a class, I usually do

 find ./ -name '*.java' -exec grep -Hin ThreadLocalHttpServletRequestProxy {} \;

and

 find ./ -name '*.xml' -exec grep -Hin ThreadLocalHttpServletRequestProxy {} \;

on our stack, for example. I think people use the Spring Tool Suite
plugin for Eclipse for things like this.

> 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 ?

> Having written that down, it sounds gnarly enough to be worth avoiding but maybe people who know Maven better can comment.

Pretty sure any dependency can be excluded and overriden.