Mailing-List: contact dev-help@sqoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@sqoop.apache.org
MIME-Version: 1.0
References: <556ECB68.2080804@apache.org>
 <905435FD-25F1-443A-948E-E595028AF7D2@apache.org>
 <CAHBV8WfV4DZN+Ji78o5EchCmFgMCHGvQvrgxX6QSpS09fN77BQ@mail.gmail.com>
 <7F91673573F5D241AFCE8EDD6A313D246046D5@SHSMSX103.ccr.corp.intel.com>
 <1A60F1A14AA475428445516E57AF7186015ADF2A@shsmsx102.ccr.corp.intel.com>
 <CAOvM-ch3_8EzJ3a97Vdx4Xrf5zXKwPPOG_Rxo=BG5Rhax2zGVA@mail.gmail.com>
In-Reply-To: 
 <CAOvM-ch3_8EzJ3a97Vdx4Xrf5zXKwPPOG_Rxo=BG5Rhax2zGVA@mail.gmail.com>
From: SHANKAR REDDY <sankara.telukutla@gmail.com>
Date: Sat, 06 Jun 2015 06:41:04 +0000
Message-ID: 
 <CA+ShD0eqAE16xfV==wYQs1QngDRJnJ87DHh6ZMgKxa0QU=osuw@mail.gmail.com>
Subject: Re: [ANN] End of life for Apache Tomcat 6.0.x
To: "dev@sqoop.apache.org" <dev@sqoop.apache.org>
Content-Type: multipart/alternative; boundary=001a1135f1a6eddd760517d3b11d

--001a1135f1a6eddd760517d3b11d
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 on jetty
On Thu, Jun 4, 2015 at 1:19 AM Abraham Elmahrek <abe@cloudera.com> wrote:

> +1 on jetty.
>
> On Thu, Jun 4, 2015 at 11:15 AM, Xu, Qian A <qian.a.xu@intel.com> wrote:
>
> > For short term, if the migration effort from tomcat 6.x to 7.x (or even
> > 8.x) is limited, we can do a migration first. For long term I vote for
> > Jetty as well. It is lightweight. Remember how complex to deploy and te=
st
> > with the mini Sqoop cluster?  Jetty will definitively make this part of
> > work easier.
> >
> > Thanks
> > Stanley (Xu, Qian)
> >
> > -----Original Message-----
> > From: Zhou, Richard [mailto:richard.zhou@intel.com]
> > Sent: Thursday, June 04, 2015 9:45 AM
> > To: dev@sqoop.apache.org
> > Subject: RE: [ANN] End of life for Apache Tomcat 6.0.x
> >
> > +1 Jetty.
> >
> >
> > Regards
> > Richard
> >
> > -----Original Message-----
> > From: Gwen Shapira [mailto:gshapira@cloudera.com]
> > Sent: Thursday, June 04, 2015 12:39 AM
> > To: dev@sqoop.apache.org
> > Subject: Re: [ANN] End of life for Apache Tomcat 6.0.x
> >
> > Maybe even upgrade to Jetty ;)
> >
> > On Wed, Jun 3, 2015 at 9:16 AM, Jarek Jarcec Cecho <jarcec@apache.org>
> > wrote:
> >
> > > We=E2=80=99re still using Tomcat 6.0.x for Sqoop, so we might need to=
 consider
> > > upgrade.
> > >
> > > Jarcec
> > >
> > > > Begin forwarded message:
> > > >
> > > > From: Mark Thomas <markt@apache.org>
> > > > Subject: [ANN] End of life for Apache Tomcat 6.0.x
> > > > Date: June 3, 2015 at 2:39:52 AM PDT
> > > > To: Tomcat Users List <users@tomcat.apache.org>
> > > > Cc: Tomcat Announce List <announce@tomcat.apache.org>,
> > > announce@apache.org, Tomcat Developers List <dev@tomcat.apache.org>
> > > > Reply-To: announce@tomcat.apache.org
> > > >
> > > > The Apache Tomcat team announces that support for Apache Tomcat
> > > > 6.0.x will end on 31 December 2016.
> > > >
> > > > This means that after 31 December 2016:
> > > > - releases from the 6.0.x branch are highly unlikely
> > > > - bugs affecting only the 6.0.x branch will not be addressed
> > > > - security vulnerability reports will not be checked against the
> > > > 6.0.x branch
> > > >
> > > > Three months later (i.e. after 30 March 2017)
> > > > - the 6.0.x download pages will be removed
> > > > - the latest 6.0.x release will be removed from the mirror system
> > > > - the 6.0.x branch in svn will move from /tomcat/tc6.0.x to
> > > > /tomcat/archive/tc6.0.x
> > > > - the links to the 6.0.x documentation will be removed from
> > > > tomcat.apache.org
> > > > - The bugzilla project for 6.0.x will be made read-only
> > > >
> > > > Note that all 6.0.x releases will always be available from the
> archive.
> > > >
> > > > It is anticipated that the final 6.0.x release will be made shortly
> > > > before 31 December 2016.
> > >
> > >
> >
>

--001a1135f1a6eddd760517d3b11d--