Changing the version of JDK used by JDeveloper
I have recently learned a quick and lazy way to change the version of the JDK used to run JDeveloper 10g R3. I am sure there is an option somewhere in the configuration screen to do the same, which I couldn't find...
While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use.
It's another step to get going with JAVA on Vista.
-ecco
While JDeveloper is not running, locate the embedded JDK on disk and rename (or delete) that directory. For me, it was C:\opt\jdev\jdk. Once it's done, restart and you will by asked to locate the version of the JDK you want to use.
It's another step to get going with JAVA on Vista.
-ecco
Comments
Configuring Support for Other JDK Versions in JDeveloper
By default, JDeveloper runs against JDK 1.4. You can develop applications in JDeveloper using other JDK versions. To configure support for application development using a different JDK:
Download the JDK version that you want from the Java Sun web site at: java.sun.com.
Unzip the JDK to a directory.
Run the following batch file to install Oracle Java Virtual Machine (OJVM) with the root of the JDK as the argument into this JDK directory: {jdev_install}/jdev/bin/InstallOJVM.bat {jdk_new_version_directory}
for the record, jdeveloper sucks balls
Tools --> Default Project Properties --> libraries --> change jdk version
Hope it'll help you all.
HKCU\Software\Oracle\JDeveloper\JDKLocation . Just edit the default value manually, or delete the key and you'll be prompted at the next start.
This way you don't have to rename your JDK, which may be in use by other applications.
InstallOJVM.bat does not do as described above. Instead, it actually installs additional Oracle files into the specified JDK. (No thanks!)
Remove directive SetJavaHome.
Start JDeveloper and you will be prompted for a JDK again.
This will set de SetJavaHome directive.
Great fix.
The JDeveloper was not even starting on JDK 1.4, let alone try to figure out a way to change the JDK :-)