Forcing JDK on first run of sqldeveloper.exe. Can this be right?
234233Jun 11 2008 — edited Oct 23 2009I've searched this forum as much as I can regarding the use of a JDK or JRE. I can get 1.5 to run just fine off an existing JRE, but only after changing the sqldeveloper.conf file, SetJavaHome property.
For some reason, the first run of 1.5 forces you to pick a java.exe that is part of a JDK. I found a thread that said the JDK was required only if using the new remote PL/SQL debugging feature. So in theory, if a developer didn't need that feature, they should be able to install the "no-jre" zip file, and point to a JRE. But the first run forces an existing JDK, with this error message:
"Cannot find a J2SE SDK installed at path: <given JRE bin path>"
I just rolled this out to 200 Java developers and QA folks this morning, so I'd like this as user-friendly as possible. I'm guessing it is a possibility to change the sqldeveloper.conf file BEFORE the first run, but since that's a mite buried, and in Unix format, that's not smooth nor seamless for the less technically-adept. 1.5 should simply be changed to not force a JDK, but instead allow the user to pick a JRE java.exe.