Forge ver. 1.4.2 is to move to Java 7. Who is not prepared?

[Chris H.]

Good to hear from you Dave. And thank you for the kind words.

I see what you mean. I did a local build of both archives and the Mac version quits when launched.

[jendave]

Good to hear from you Dave. And thank you for the kind words.

I see what you mean. I did a local build of both archives and the Mac version quits when launched.

Yes. I got the same result. There is another jar bundler called "appbundle" that is supposed to work on Java7 and the latest OSX releases. I will work on getting that into the build process.

[Agetian]

I'm fully prepared, I've been using JDK 7 for quite a while by now and had no issues with it whatsoever, the latest Forge SVN builds also build fine on my end.

@ Chris: Sorry to hear you're going through difficult times... Please get better soon and I wish your wife a fast recovery!

[Max mtg]

Good to hear from you Dave. And thank you for the kind words.

I see what you mean. I did a local build of both archives and the Mac version quits when launched.

Yes. I got the same result. There is another jar bundler called "appbundle" that is supposed to work on Java7 and the latest OSX releases. I will work on getting that into the build process.

Thanks, Dave!
I would never set up the mac bundles alone.

[Chris H.]

[quote="Chris H."]The Java Compiler section allowed me to change the Java Build Path and I see a warning that "The 1.7 compiler compliance level is not yet supported." This may require a version of Eclipse that is newer than 3.7.0./quote]
 
I have a few minor problems with my approach.

I am using an old version of Eclipse 3.7.0 and the Project -> Properties section does not have a complier compliance option for Java 7. It only goes up to 1.6.

I tried to use the Help -> Check for Updates option but it will not update Eclipse. I end up with a problem occurred dialog:

No repository found at http://eclipse-cs.sourceforge.net/update/site.xml.