On Mon, Oct 5, 2015 at 10:11 PM, Martin Grigorov <mgrigo...@apache.org> wrote: > Now even with Martijn's commit (remove Servlet 3.1 methods) the build still > fails because Jetty 9.3 (and even 9.2.x) requires 3.1.0. > > Any preferences what to do? > a) use Jetty 8.x > b) use Servlet 3.1.0 > > I personally am for b). By the time we reach to 8.0.0 this should be fine > for most apps out there :-)
We gain support for jetty 9, but drop support for any JavaEE 6 deployable. Servlet 3.1 is JavaEE 7. Apps that require servlet 3.0 and JavaEE 6 will still have Wicket 6.x and 7.x to build against for the foreseeable future, so I don't think it would be very hard to drop servlet 3.0 and Java EE 6. My guess is most supported contracts for Java EE 6 containers don't have a provision for Java 8, so they can't upgrade anyhow. Before I cast my vote, I'd like to wait for more opinions... Martijn
