For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 1 reply, 2 voices, and was last updated 18 years, 11 months ago by
.
-
Posts
-
I have Eclipse 3.2.1 and MyEclipse 5.1 GA. My JUnit tests exhibit un-patched DST behaviour when run from an ant script started from the Eclipse GUI, but not when run from inside the GUI using “Run as JUnit ..”.
I have traced the problem down to the ant script JUnit tests running on the embeded 1.5.0_08 JRE in MyEclipse. When launced from the Eclipse GUI, this JVM is used for JUnit regardless of what JVM is running the Eclipse GUI or the ant script itself. This JVM choice is controlled by the copy of JUnit shipped with MyEclipse, it seems?
Is there a way to force MyEclipse to use the same JVM as Eclipse itself for JUnit tests? Or the same one as the launched JVM process running my ant script?
Finally, is there an update to MyEclipse with a DST-fixed JVM embeded in it?
Eclipse GUI, but not when run from inside the GUI using “Run as JUnit ..”
By “Eclipse GUI” do you mean the Ant view and the Run button on the top of it?
Is there a way to force MyEclipse to use the same JVM as Eclipse itself for JUnit tests? Or the same one as the launched JVM process running my ant script?
Sure, you can edit the shortcut used to start MyEclipse and using the -vm command line argument, point it at a different VM, like this:
eclipse.exe -vm C:\Program Files\Java\jdk1.5.0_11\bin\javaw.exe -vmargs <ARGUMENTS>
