Community
Participate
Working Groups
Now that Jetty is an Eclipse project and is part of the release train, we should really be building/shipping the release train version of Jetty for future releases. I'm opening this bug against UA to explore what implications that might have for the help system.
I think that it is a good idea to move to newer versions of Jetty as they are available. See Bug 306920 for an example of a bug that has been fixed in Jetty but is still in Eclipse because we are using an older version of Jetty. I can't think of why we would not want to do this.
Also see bug309529.
Chris, we have started discussing moving to Jetty 8 in Eclipse PMC calls. We didn't have a good feel for the impact on UA for this move. Can do you some initial investigation and give us an idea on much work is involved here? There are impacts on several teams so we'll need to move early in Juno if we are going to do it.
(In reply to comment #3) The only area of impact is that Jetty 8 uses Servlet 3.0. There is one specific impact on the UA tests - compilation errors in org.eclipse.ua.tests.help.webapp.MockServletRequest which implements HttpServletRequest and is used to test the reading and writing of cookies. Other than that there is nothing about UA or the UA extension points which will present any issues that could not be encountered by any client of the Equinox server. Clients that write their own servlets need to make sure that their version dependencies on javax.servlet and javax.servlet.http are not overly restrictive. I don't see any good alternative to moving forward to using Jetty 8.
Thanks Chris!
By chance, I happened across this old bug. Since Jetty is not part of "release train", per se (any longer) I think fair to close as "won't fix" ... though, the intent is pretty much covered in bug 453910 -- for Mars, at least.