[java-parent-projects COMMIT] /java-parent-project-v3/trunk/pom.xml

[Ian Young]

On 22 May 2014, at 16:12, Brent Putman <putmanb at georgetown.edu> wrote:

> That's the part that that I'm not clear on. I don't have much experience with Jetty.  Does Jetty 9.1/9.2 *require* the app the be written to the servlet 3.1 spec?  That would sound atypical to me.

I agree, I don't see that any such thing can be *required* as you'd lose all backwards compatibility.

> If we don't actually need servlet 3.1, then we're unnecessarily limiting the containers people can deploy in.

Yes, severely. Which is why when we discussed this before, we decided that 3.1 was a step too far.

> On the other hand, if there are 3.1 features we want to use, then that's another story entirely.

Yep. But I don't think that's the case. Or at least, if it is the case then we need to be very specific and have a lot more scrutiny over the feature we think we might want to use to make sure that forcing people to (say) Tomcat 8 -- which is not even a stable release yet, just a beta -- is justified.

	-- Ian



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/dev/attachments/20140522/6c7c8bc4/attachment.html 
-------------- 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/20140522/6c7c8bc4/attachment.bin