I deinstalled the Java Virtual Machine on my OS X machine to see if Servoy 7.4.3 still needs Java 1.6.0. It seems so as a dialog appeared to download Java 1.6. I thought I read in the Servoy forum that Servoy Developer doesn’t need Java 1.6 any more. Not true?
Servoy 7.4.3 does not need Java 1.6…
it runs fine under Java 7 & 8, there is an issue, with the latest Java 8 wit Yosemite. (you can’t get the cursor into fields)
you can workaround it: viewtopic.php?f=11&t=20808&p=111681&hilit=oracle#p111722
I uninstalled Java 1.6 in /System/Library/Java/JavaVirtualMachines/ so there is no Java installed at all any more on my Mac (and also no Java Developer Previews in /Library/Java/JavaVirtualMachines/).
Then I start Servoy Developer and get the attached dialog. I would have expected a dialog telling me to install the current JVM, not version 1.6.
Harjo:
Servoy 7.4.3 does not need Java 1.6…
it runs fine under Java 7 & 8, there is an issue, with the latest Java 8 wit Yosemite. (you can’t get the cursor into fields)
you can workaround it: viewtopic.php?f=11&t=20808&p=111681&hilit=oracle#p111722
do you have any other Java Version installed on your Mac?
I did the same as you to uninstall Java 6 but installed Java 8 bevor starting Servoy Developer.
For me it’s working, but I don’t know where I can detect under wich Java version the Servoy Developer is running!?
BTW I’m still on OS X 10.9.5.
Regards
EDIT:
I have still Java 1.6.0.jdk in /System/Library/Java/JavaVirtualMachines/.
But “java -version” in the Terminal returns “build 1.8.0_40”. Thought Servoy Dev. ist running with this JRE, but I’m obviously wrong!?
So it seems to run on Java 1.8.0_x.
But then I am wondering why is the Servoy Developer asking to install Java 1.6.0 when this Java version is not installed? I have to install Java 1.6, as otherwise Servoy Developer does not run.
OS X 10.9.5
Servoy Developer 7.4.3
There is Java 1.6.0 (need, see above) and Java 1.8.0 installed
Regards,
jcompagner:
you can see exactly where the developer runs with if you open the Help->About->Installation details ->Configuration
there you see a textarea with all the java options that are currently there/set
The Application Server and the Servoy Developer Version 7.4.4 are still asking for Java 1.6 on OS X and not starting if one doesn’t install Java 1.6. Can you please have a look at this problem again - thanks a lot!
what i don’t get is your comment about the “application server”
that will for sure not ask for a java 1.6 thats just an .sh file that just starts “java xxxxxxxxx”
But if you do a clean install of server 7.4 .4 so get the installer and install a brand new clean install
then if you start the developer it wants java 6?
We are not talking here about a upgraded one, because upgrading does only upgrade plugins not the exe or anything related to the “app”
With the hint to the Application Server I meant a stand alone Application Server will not start if no Java 6 is present. With stand alone I mean the Application Server which is not started by the Sevoy Developer, but started for example on OS X by the launch daemon and the launchctl list. For example with following line
I just tested 7.4.3 and 7.4.4 on a Mac OS X 10.10 environment with Java 7 on it and both versions don’t ask for Java 6.
I tried both Developer and Server and both run without any issues.
The fact that Servoy server is not running for you might suggest there is something else going on. You say you uninstalled the Java Virtual Machine, do you still have Java 7/8 installed? Perhaps some symlinks/environment variables are not pointing to the Oracle JVM(s).
Thanks for testing. I have the current Java 8 installed. Are you aware of a way to check the sys links and environment variables? I am going to check with a clean installation of the Developer (was not aware there is a difference between updated and clean installation concerning the Developer).
Not sure if this will help but I had this issue immediately after I upgraded to OS X 10.10.4. Prior to the upgrade Servoy developer (7.4.4) was running perfectly with no Java 6 installed but after the upgrade, as soon as I started Developer, it gave me the message you have above. A simple reboot of the affected machine restored everything to working order again.