Community
Participate
Working Groups
IBM 1.4 series VMs no longer keep all Java classes in an rt.jar file. Instead, they are broken up across seven different files, core.jar, graphics.jar, security.jar, etc. Should we add a new VM install type so that users don't have to manually add these seven jar files to the classpath?
It sounds like we need an "IBM 1.4.x" VM install type to handle this. It should mostly be a simple subclass of the standard VM install type.
*** Bug 21765 has been marked as a duplicate of this bug. ***
*** Bug 23920 has been marked as a duplicate of this bug. ***
The jars that appear on the bootpath by default are (As found by the system property "sun.boot.class.path"): core.jar graphics.jar security.jar server.jar xml.jar charsets.jar (I wonder if the org.apache.xerces will conflict with the version in Eclipse - i.e. in xml.jar).
Fixed. The StandardVMType now recognizes and handles IBM 1.4 type VMs. Please verify Darin W.
Found that the new support which uses "java -version" to determine which libraries to use, causes DOS consoles to open/close. Not sure what happens on linux.
Fixed console problem. Also implemented caching of the 'java -version' output for performance. There is still one odd problem I can't pin down. The progress monitor doing a VM search in the pref. dialog now acts like each VM is a new search, where as it used to just crawl from left to right once for all VMs. This seems like it might hurt performance. Will investigate.
It looks like we're explicitly subTasking each new potential install location. Maybe it's more noticeable now that searching is slower.
Please verify, Darin W.
The VM search works, but launching 1.4 failed: NOTE: the command line is trying invoke a javaw in \bin, but my install does not have a \bin. I only have \jre\bin. !ENTRY org.eclipse.debug.ui 4 120 Oct 11, 2002 09:03:23.733 !MESSAGE Error logged from Debug UI: !STACK 1 org.eclipse.core.runtime.CoreException[150]: java.io.IOException: CreateProcess: D:\ibm1.4\bin\javaw -classpath d:\testspaces\test- space\JUnit\bin;d:\testspaces\test-space\JUnit\junit3.8.1\junit.jar -Xdebug - Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:7242 junit.samples.VectorTest error=2 at java.lang.Win32Process.create(Native Method) at java.lang.Win32Process.<init>(Win32Process.java:63) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:566) at org.eclipse.jdt.launching.AbstractVMRunner.exec (AbstractVMRunner.java:72) at org.eclipse.jdt.internal.launching.StandardVMDebugger.run (StandardVMDebugger.java:181) at org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunchConfigurationDelega te.launch(JavaLocalApplicationLaunchConfigurationDelegate.java:97) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConfiguration.java:140) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog$11. run(LaunchConfigurationDialog.java:2283) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run (ModalContext.java:98) !ENTRY org.eclipse.jdt.launching 4 150 Oct 11, 2002 09:03:23.743 !MESSAGE Exception starting process: D:\ibm1.4\bin\javaw -classpath d:\testspaces\test-space\JUnit\bin;d:\testspaces\test-space\JUnit\junit3.8.1 \junit.jar -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:7242 junit.samples.VectorTest !STACK 0 java.io.IOException: CreateProcess: D:\ibm1.4\bin\javaw -classpath d:\testspaces\test-space\JUnit\bin;d:\testspaces\test-space\JUnit\junit3.8.1 \junit.jar -Xdebug -Xnoagent -Djava.compiler=NONE - Xrunjdwp:transport=dt_socket,suspend=y,address=localhost:7242 junit.samples.VectorTest error=2 at java.lang.Win32Process.create(Native Method) at java.lang.Win32Process.<init>(Win32Process.java:63) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:566) at org.eclipse.jdt.launching.AbstractVMRunner.exec (AbstractVMRunner.java:72) at org.eclipse.jdt.internal.launching.StandardVMDebugger.run (StandardVMDebugger.java:181) at org.eclipse.jdt.internal.launching.JavaLocalApplicationLaunchConfigurationDelega te.launch(JavaLocalApplicationLaunchConfigurationDelegate.java:97) at org.eclipse.debug.internal.core.LaunchConfiguration.launch (LaunchConfiguration.java:140) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationDialog$11. run(LaunchConfigurationDialog.java:2283) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run (ModalContext.java:98)
The issue is now with the StandardVMRunner/Debugger. It does not account for a jre install without a "bin" (i.e. a JRE vs and SDK).
OK, think I got it this time. the vm runner tries jre/bin, then bin.
Please verify (yet again) Darin W.
Verified.
