Yes, Srikanth. Lens runs fine with java8 runtime. But it needs to be
documented in deployment guide.

On Wed, May 13, 2015 at 11:12 AM, Srikanth Sundarrajan <[email protected]>
wrote:

> IMHO, As a bare minimum, we need to support LENS to run on Java8. Using
> java7 for compilation in the interim till we sort out issues with java 8
> should be largely acceptable.
>
> Regards
> Srikanth Sundarrajan
>
> > Date: Wed, 13 May 2015 10:26:41 +0530
> > Subject: Re: Move to Java 7?
> > From: [email protected]
> > To: [email protected]
> >
> > I propose, we support compiling with java7 for some more time. Few
> reasons
> >
> >    1. Most of the production setup is still with java7.
> >    2. Lens build with java8 has some issues. We are not sure we uncovered
> >    all.
> >    3. Many projects work with java7 and most of us have java7 in our
> >    machines.
> >
> > What do others think?
> >
> > Thanks
> > Amareshwari
> >
> > On Wed, Jan 21, 2015 at 12:03 PM, Jaideep Dhok <[email protected]>
> > wrote:
> >
> > > That would be even better.
> > >
> > > On Wed, Jan 21, 2015 at 12:00 PM, Srikanth Sundarrajan <
> > > [email protected]>
> > > wrote:
> > >
> > > > Hi Jaideep,
> > > >     Java7 EOL is already announced, can we consider Java 8 instead ?
> > > >
> > > > Regards
> > > > Srikanth Sundarrajan
> > > >
> > > > > Date: Wed, 21 Jan 2015 11:55:13 +0530
> > > > > Subject: Move to Java 7?
> > > > > From: [email protected]
> > > > > To: [email protected]
> > > > >
> > > > > Hi all,
> > > > > I was thinking we should move to Java 7 as the compiler version and
> > > start
> > > > > using niceties like try with resources.  I think most devs are
> already
> > > > > using Java 7 to build and develop but the version in POM is still
> 1.6.
> > > > >
> > > > > Java 7 is already officially supported by Hadoop 2.x
> > > > >
> > > > > Thoughts?
> > > > >
> > > > > Thanks,
> > > > > Jaideep
> > > > >
> > > > > --
> > > > > _____________________________________________________________
> > > > > The information contained in this communication is intended solely
> for
> > > > the
> > > > > use of the individual or entity to whom it is addressed and others
> > > > > authorized to receive it. It may contain confidential or legally
> > > > privileged
> > > > > information. If you are not the intended recipient you are hereby
> > > > notified
> > > > > that any disclosure, copying, distribution or taking any action in
> > > > reliance
> > > > > on the contents of this information is strictly prohibited and may
> be
> > > > > unlawful. If you have received this communication in error, please
> > > notify
> > > > > us immediately by responding to this email and then delete it from
> your
> > > > > system. The firm is neither liable for the proper and complete
> > > > transmission
> > > > > of the information contained in this communication nor for any
> delay in
> > > > its
> > > > > receipt.
> > > >
> > >
> > > --
> > > _____________________________________________________________
> > > The information contained in this communication is intended solely for
> the
> > > use of the individual or entity to whom it is addressed and others
> > > authorized to receive it. It may contain confidential or legally
> privileged
> > > information. If you are not the intended recipient you are hereby
> notified
> > > that any disclosure, copying, distribution or taking any action in
> reliance
> > > on the contents of this information is strictly prohibited and may be
> > > unlawful. If you have received this communication in error, please
> notify
> > > us immediately by responding to this email and then delete it from your
> > > system. The firm is neither liable for the proper and complete
> transmission
> > > of the information contained in this communication nor for any delay
> in its
> > > receipt.
> > >
>
>

Reply via email to