|
|
Post by Lars Ericson on Jul 17, 2015 16:16:26 GMT -8
I tried running GGP Base with Java 8 in hopes of faster garbage collection and it doesn't work. Also I tried running a downloaded gephi (http://gephi.github.io/) with Java 8 installed and it didn't work until I uninstalled Java 8 and installed Java 7. What's up with that, does anybody know the main sources of incompatibility between Java 7 and 8, for GGP? In general there is a synopsis here but I'm not sure which parts are hitting GGP: www.oracle.com/technetwork/java/javase/8-compatibility-guide-2156366.html#A999387 |
|
|
|
Post by Steve Draper on Jul 18, 2015 5:30:00 GMT -8
I am running with Java 8 and ggp-base without issues, so I cannot usefully comment on this. Are you using the most recent ggp-base (i.e. - from GIT rather than from a ZIP posted somewhere?)
|
|
|
|
Post by Jarrod Torriero on Jul 18, 2015 5:46:29 GMT -8
The Eclipse project for ggp-base is configured to compile with Java 7. Did you change that, or were you just trying to run an unmodified ggp-base compile with Java 7 not installed (which I'm pretty sure wouldn't work)? To get ggp-base to use Java 8 (which did indeed result in a speed improvement for me) I had to do the following:
1. Install Java 8.
2. Add the Java 8 JRE in Eclipse (Window->Preferences->Java->Installed JREs).
3. Change the ggp-base build path (ggp-base Properties->Java Build Path), removing the 1.7 JRE and adding the 1.8 one.
4. In the 1.8 JRE added to the build path in step 3, add the following access rule:
Accessible: com/sun/net/httpserver/**
5. You may need to change the compiler setting for ggp-base (ggp-base Properties->Java Compiler) to use Java 8, if that doesn't happen automatically.
After I did all that, it worked fine, and with small speed improvements in every game I tried.
|
|
|
|
Post by Lars Ericson on Jul 18, 2015 7:02:13 GMT -8
Thanks, I will try that. What I did was uninstall Java 7, install Java 8, and try to run Gephi and Server, where both were built for Java 7. Both failed silently.
I was operating under the premise that JVM is JVM and a new JVM should be backwards compatible, if the JAR was packed with everything it needs, which I assume is the case because I can move a Windows-built JAR to Linux and it works.
Above steps will no doubt rectify the situation.
|
|
|
|
Post by Jarrod Torriero on Jul 18, 2015 8:10:57 GMT -8
To be clear, I'd never used Java prior to the Coursera course and even now I'm pretty much learning as I go, so you should take my comments on such matters with a grain of salt. However, the steps I listed above did work for me, so I expect they'll work for you too.
|
|
|
|
Post by Steve Draper on Jul 18, 2015 10:28:44 GMT -8
To be clear, I'd never used Java prior to the Coursera course and even now I'm pretty much learning as I go, so you should take my comments on such matters with a grain of salt. However, the steps I listed above did work for me, so I expect they'll work for you too. I learnt Java on/because of the GGP course also. Glad to see someone else in the same boat (I preferentially use it for several other things now too - been amazed really at how good the JVM is at optimizing) |
|
|
|
Post by alandau on Jul 18, 2015 12:47:29 GMT -8
If you get another error, can you post the error message or stacktrace? Otherwise there's not much to go on.
JVMs should be able to run Java code compiled in previous versions.
EDIT: You said they failed silently. How were you running them? From the console? In Eclipse? Double-clicking on an icon?
|
|
