We can move when Hadoop does.
HOWEVER, it should be the same version used by downstream or we will have
Furthermore, any refactoring from 6 to 7 may well need to be done through
shims in hadoop-compat modules unless all branches of Hadoop that we
support have a release that moves to Jetty 7 (or 9 or whatever).
I think we should wait at least until Hadoop makes a move, or if there is a
critical reason to do otherwise on our own initiative.
On Fri, May 3, 2013 at 12:36 PM, Jean-Marc Spaggiari <
[EMAIL PROTECTED]> wrote:
> There is some plans for Hadoop to move to Jetty 7.
> Will that impact us? Might be the opportunity to move HBase to 9?
> 2013/5/3 Andrew Purtell <[EMAIL PROTECTED]>
> > I would say there has not been a volunteer yet willing to do that
> > refactoring and contribute it? Will updating our Jetty dependency cause
> > classpath conflicts with Hadoop core code that also uses jetty? We
> > some of their servlets. Does that mean Hadoop core would also need to
> > update and refactor?
> > On Friday, May 3, 2013, Julian Zhou wrote:
> > > Is there any plan to migrate Jetty from version 6.1.26 (current version
> > > in trunk) to version 9, which has been moved org.eclipse pkg? There are
> > > lots of refactoring and new APIs for HTTP/Servlet/XML related in
> > > 9, which might be able to benefit future HBase development and
> > >
> > > Thanks~
> > >
> > > --
> > > Best Regards, Julian
> > >
> > >
> > --
> > Best regards,
> > - Andy
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)