|Re: [jetty-users] Jetty and Java 11|
Hi, On Mon, May 7, 2018 at 10:04 AM, Lord Buddha <lord.buddha@xxxxxxxxx> wrote: > Simone, > > am also concerned about there being an early Jetty release for Java 11. > The reason for this being Java 8 being end of life in January, and perhaps > like other companies have a change freeze over the holiday season meaning > very little time to move large applications to a new supported/maintained > platform. You don't need to, and companies have to plan for this. > The move to Java 11 comes with the removal of the deprecated jvm modules > introduced in Java 9. So am wanting to see what of those deprecated > modules Jetty must now supply... and perhaps what it might optionally > supply. > > e.g. > > java.xml.ws > java.xml.ws.annotation > > I assume that with Java 11 that containers such as Jetty would need to > supply these. But, would you also supply java.xml.bind & java.activation. > > Am I off the mark here ? Others may chime in, but in my view it's not Jetty (or any container) that should provide those modules. If you need them in your application, just put them in WEB-INF/lib. Or, with Jetty, you can easily write a Jetty module that puts them in the server classpath if you really need them that way. -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts.
Back to the top