From: Greg W. <gr...@mo...> - 2008-12-06 09:00:52
|
Juancarlo Añez wrote: > Greg, > > On my part, it's your call. > > One of the risks I see is that eclipsefying Jetty could make it more > complex, when one of the hallmarks of Jetty is simplicity and minimalism. Juancarlo, that indeed was one of my initial fears - that eclipse would expect changes to the core of Jetty and perhaps OSGi dependencies. But in my discussions with them, it has become clear that they truly are component minded, and that while they are keen for Jetty to better work with OSGi, they are not about to insist that we change the core. However, I actually see the effort to become more OSGi friendly as a way to increase the simplicity and minimalism of Jetty. Building Jetty as an app server tends to allow extra dependencies to develop and we've probably made a few packaging mistakes in the past with Jetty. Renewing our focus on components, will mean that we need to cleanup those dependencies and packaging somewhat, so that Jetty - already very modular - will become even more so. I see the focus of the project at eclipse would be to build great HTTP and servlet components. The Jetty hightide project would remain at codehaus and would be focused on providing a great application server, built from the eclipse (and other) components. cheers |