Spring 4 and Servlet 3.0

[Ian Young]

On 17 Dec 2013, at 01:12, Tom Zeller <tzeller at dragonacea.biz> wrote:

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

>> 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 overridden.

Yes, but the issue here is whether that will actually do what we want. Part of the reason it's not obvious that it will is that our *tests* exercise a part of Spring V4 that actually does require the newer dependency, and won't work with 2.5. The other complication is that the 2.5 and 3.0 servlet APIs have different Maven coordinates (javax.servlet:servlet-api vs. javax.servlet:javax.servlet-api).

	-- Ian



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5943 bytes
Desc: not available
Url : http://shibboleth.net/pipermail/dev/attachments/20131217/92754fae/attachment.bin