Community
Participate
Working Groups
Build: 2.1 RC1 This is a spin-off from bug 33412. This bug deals with the fact that the automatic JAR detection fails when the JRE is under a path containing GB18030 characters. Here are the steps: 1) Install an IBM 1.4.0 JRE in a directory that contains GB18030 characters in the path. 2) Install eclipse in a directory that does NOT contain GB18030 chars. 3) Launch eclipse using a JRE that does NOT contain GB18030 chars. 4) Under Preferences > Java > Installed JREs, add a new JRE. 5) Select the JRE that is located under the GB18030 path Observe: it fails to correctly detect all the required system libraries. It finds all the libraries under the "ext" directory, but fails to find the basic liraries (core.jar, security.jar, xml.jar, etc). The log file contains a stack trace (log attached).
Created attachment 3845 [details] Log file containing stack trace
John, what happens if you Eclipse on a Sun 1.4.1 VM, or an IBM 1.4 VM? I believe this is a VM limitation.
I will investigate a bit further. I also suspect this is a VM limitation.
Deferred. However, any more input is appreciated (this may not be a debug problem - it might be a class library issue).
Sorry, I thought I had already followed up to this. You guys are forking a new "java" process to detect the JARs. Trying to run any java program when the java runtime is installed in a GB18030 directory will fail. For example: - install JRE in c:\??\jre (where ?? is a GB18030 char) - put a HelloWorld.class file in c:\temp - try to run HelloWorld using the jre from c:\??\jre -> Fails to create VM. So, this is definitely a VM limitation. I tried this on a variety of 1.3 and 1.4 JREs and JDKs from IBM and Sun.
marking as a README. Will not fix.
won't fix.
