For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 2 replies, 2 voices, and was last updated 21 years, 8 months ago by
.
-
Posts
-
Hi,
Since I was told that debugging in Eclipse/MyEclipse might be very problematic with Java 5, I just re-installed the jdk 1.4.2_06.
The problem is that my machine still thinks (at least typing “Java -version” in a DOS window) it’s using version 5.0.
Therefore, my questions are these:
1. Can I “point” MyEclipse/Eclipse to the 1.4.2 release of the JDK and leave the JDK 5.0 installed? I don’t see how to do this from project properties and looking at the various compiler settings.
2. If I have to un-install version 5.0 (based on what you say in #1), will that screw up MyEclipse that “thinks” it’s using version 5 or is there some simple workaround.
I don’t want to hose the MyEclipse setup.
In JBuilder, my old environment (I like MyEclipse much better!), it was simple to add as many JDK as you wanted.
Getting the debugging to work completetly has been a pain under the JDK 5.0. I’m very hopeful that once I resolve this issue, things will smooth out a bit.
I look forward to any and all replies.
Thanks!!!
— M
8)
1) Yes, you use the -vm command line argument to Eclipse, like so:
eclipse.exe -vm c:\j2sdk1.4.2_06\bin\javaw.exe2) No need to unisntall, just tell Eclipse which one to use.
In JBuilder, my old environment (I like MyEclipse much better!), it was simple to add as many JDK as you wanted.
It is easy to add multiple JREs/JDKs in Eclipse as well, this is just an issue of the JRE that is being used to actually run Eclipse, that is whta we are trying to change here. This requirement about carying which JRE is used to run Eclipse will be removed in a future release. Sorry for the trouble.
Getting the debugging to work completetly has been a pain under the JDK 5.0. I’m very hopeful that once I resolve this issue, things will smooth out a bit.
No doubt, Eclipse and MyEclipse 3.0.x and 3.8.x (respectively) are not tested to be run on JDK 5.0; so weirdness is possibly expected with as big a release as JDK 5.0 was.
