Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

check with java 1.7 -- is 1.8 really a prereq #5

Open
namato opened this issue Aug 23, 2016 · 5 comments
Open

check with java 1.7 -- is 1.8 really a prereq #5

namato opened this issue Aug 23, 2016 · 5 comments

Comments

@namato
Copy link
Contributor

namato commented Aug 23, 2016

per Paul the sandbox VMs still have 1.7 and it currently fails to compile after updating pom.xml

@tdunning
Copy link
Collaborator

It is a pre-requisite for the code that I wrote.

Can probably be backed down, especially with help from IntelliJ.

On Tue, Aug 23, 2016 at 12:14 PM, Nick Amato [email protected]
wrote:

per Paul the sandbox VMs still have 1.7 and it currently fails to compile
after updating pom.xml


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAPSeoNkvWYlL8HvKOafD7wnnWnRoTlMks5qi0aSgaJpZM4JrSKC
.

@tdunning
Copy link
Collaborator

The bigger question is why we are shipping with a version of Java that went
to end of life over a year ago

On Tue, Aug 23, 2016 at 2:04 PM, Ted Dunning [email protected] wrote:

It is a pre-requisite for the code that I wrote.

Can probably be backed down, especially with help from IntelliJ.

On Tue, Aug 23, 2016 at 12:14 PM, Nick Amato [email protected]
wrote:

per Paul the sandbox VMs still have 1.7 and it currently fails to compile
after updating pom.xml


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAPSeoNkvWYlL8HvKOafD7wnnWnRoTlMks5qi0aSgaJpZM4JrSKC
.

@caroljmcdonald
Copy link

MapR 5.2 sandbox

[user01@maprdemo ~]$ java -version

java version "1.7.0_79"

OpenJDK Runtime Environment (rhel-2.5.5.4.el6-x86_64 u79-b14)

OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

On Tue, Aug 23, 2016 at 5:05 PM, Ted Dunning [email protected]
wrote:

The bigger question is why we are shipping with a version of Java that went
to end of life over a year ago

On Tue, Aug 23, 2016 at 2:04 PM, Ted Dunning [email protected]
wrote:

It is a pre-requisite for the code that I wrote.

Can probably be backed down, especially with help from IntelliJ.

On Tue, Aug 23, 2016 at 12:14 PM, Nick Amato [email protected]
wrote:

per Paul the sandbox VMs still have 1.7 and it currently fails to
compile
after updating pom.xml


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5, or mute
the
thread
<https://github.com/notifications/unsubscribe-auth/
AAPSeoNkvWYlL8HvKOafD7wnnWnRoTlMks5qi0aSgaJpZM4JrSKC>
.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#5 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADMEZG8wGoDhd8cqcc4A7t8Yo6Lo5uoQks5qi2CvgaJpZM4JrSKC
.

@tdunning
Copy link
Collaborator

I believe in the fact of the matter.

My question was "Why?"

@tdunning
Copy link
Collaborator

I looked at the code. Looks like the issues are all with non-final variables in closures. This should be easy to fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants