-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
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]
|
The bigger question is why we are shipping with a version of Java that went On Tue, Aug 23, 2016 at 2:04 PM, Ted Dunning [email protected] wrote:
|
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]
|
I believe in the fact of the matter. My question was "Why?" |
I looked at the code. Looks like the issues are all with non-final variables in closures. This should be easy to fix. |
per Paul the sandbox VMs still have 1.7 and it currently fails to compile after updating pom.xml
The text was updated successfully, but these errors were encountered: