Community
Participate
Working Groups
Build Identifier: 20100917-0705 Hello, due to an J2ME project I decided to set Java 1.3 as compiler setting. But with a JDK for Java 1.6, I got a warning (buildpath problem). So I decided to install a JDK for Java 1.3. So I went to the Oracle homepage, Downloaded it and, installed and added it to the Installed JRE's in Eclipse. But when selecting the execution environments (I selected each single one: the CDC's, OSGI's, J2SE's and JavaSE's ones), I never can choose the jdk 1.3 as execution environment. I also tried Java 1.3 JRE instead of SDk, same result. It seems that these JDK's while they can be set up as installed JRE's never match an execution environment. Reproducible: Always Steps to Reproduce: I don't know if steps 1. and 2. are necessary. 1. Have a Java Project with Java 1.6 compliance settings 2. Change the settings to Java 1.3 compliance 3. Install JDK/JRE 1.3.1_20
I also check the logfile et voila, there are some stacktraces. I only copied the relevant ones cause I'm also getting exceptions due to other plugins (Subclipse :-( ). If required I can attach more /the whole file. !ENTRY org.eclipse.jdt.launching 4 4 2010-10-11 15:20:27.252 !MESSAGE Unable to retrieve system properties !STACK 1 org.eclipse.core.runtime.CoreException: Unable to retrieve system properties at org.eclipse.jdt.launching.AbstractVMInstall.abort(AbstractVMInstall.java:490) at org.eclipse.jdt.launching.AbstractVMInstall.evaluateSystemProperties(AbstractVMInstall.java:440) at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironmentAnalyzer.isFoundation1_0(ExecutionEnvironmentAnalyzer.java:142) at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironmentAnalyzer.analyze(ExecutionEnvironmentAnalyzer.java:90) at org.eclipse.jdt.internal.launching.environments.Analyzer.analyze(Analyzer.java:40) at org.eclipse.jdt.internal.launching.environments.EnvironmentsManager.analyze(EnvironmentsManager.java:334) at org.eclipse.jdt.internal.launching.environments.EnvironmentsManager.vmAdded(EnvironmentsManager.java:373) at org.eclipse.jdt.launching.JavaRuntime.fireVMAdded(JavaRuntime.java:2312) at org.eclipse.jdt.launching.JavaRuntime.initializeVMs(JavaRuntime.java:2682) at org.eclipse.jdt.launching.JavaRuntime.getVMInstallTypes(JavaRuntime.java:519) at org.eclipse.jdt.internal.launching.environments.EnvironmentsManager.initializeCompatibilities(EnvironmentsManager.java:233) at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.init(ExecutionEnvironment.java:178) at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.getDefaultVM(ExecutionEnvironment.java:215) at org.eclipse.jdt.internal.launching.JREContainerInitializer.resolveVM(JREContainerInitializer.java:171) at org.eclipse.jdt.internal.launching.JREContainerInitializer.resolveVM(JREContainerInitializer.java:138) at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize(JREContainerInitializer.java:57) at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2707) at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2613) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2653) at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1845) at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:2705) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2645) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2783) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1915) at org.eclipse.jdt.internal.core.JavaProject.isOnClasspath(JavaProject.java:2193) at org.eclipse.jdt.internal.ui.BuildpathIndicatorLabelDecorator.getOverlay(BuildpathIndicatorLabelDecorator.java:47) at org.eclipse.jdt.internal.ui.BuildpathIndicatorLabelDecorator.decorate(BuildpathIndicatorLabelDecorator.java:34) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:269) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 org.eclipse.jdt.launching 4 150 2010-10-11 15:20:27.252 !MESSAGE Unable to retrieve system properties !ENTRY org.eclipse.jdt.launching 4 4 2010-10-11 15:24:39.669 !MESSAGE Failed to retrieve default libraries for /opt/jre1.3.1_20
Move to JDT/Debug
I installed the 1.3.1_20 JDK, but I did not get the shown exception. Do you have other JREs installed? Generally this exception indicates that you have a JRE installed (in the prefereces) that is not executable.
I have only installed JDK 1.6.0_18 (default) when I installed the JDK / JRE 1.3. When installing JDK 1.3 at first everything seems to be fine, it shows /opt/jdk1.3.1_20/jre/lib/rt.jar as JRE system library with the src.jar as location of sourcecode correctly set. Can I check anything further?
I guess you could try a new workspace and see if the same exception occurs when adding the 1.3.1 JRE. (I was testing the scenario on WinXP - are you using Linux?)
(In reply to comment #5) > I guess you could try a new workspace and see if the same exception occurs when > adding the 1.3.1 JRE. (I was testing the scenario on WinXP - are you using > Linux?) as chosen above: Ubuntu Linux 10.04 32bit on acer travelmate 5320 (intel core 2 duo celeron, 3 GB RAM (extende, default is less)). Okay I'll try a new workspace tomorrow thanks
Hi, I have tested it with a new workspace. => Started Eclipse 3.6.1, choose a new workspace (it was actually running on my default workspace in another Eclipse instance) by typing a name in the dialog for choosing the workspace at startup. => JDK 1.6.0_18 (my default Java, hadn't upgraded until now) was already there, added the JDK 1.3.1_20 => checked the complete log (it jsut contains the text below) !SESSION 2010-10-14 18:34:09.995 ----------------------------------------------- eclipse.buildId=M20100909-0800 java.version=1.6.0_18 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os linux -ws gtk -arch x86 -product org.eclipse.epp.package.jee.product !ENTRY org.eclipse.jdt.launching 4 4 2010-10-14 18:35:48.479 !MESSAGE Failed to retrieve default libraries for /opt/jdk1.3.1_20
I forgot one thing: Is is normal for JDK 1.3.1_20 to have only rt.jar on board? With newer JDK I have some more libraries and the log is complaining about missing libraries ...
Are you referencing the JRE via a symlink? (perhaps a dup of bug 281495).
I don't use a symlink for JDK 1.3.1_20 My default JDK is provided by a symlink + environment variables which is probably the reason for it to show up as installed in a new workspace. But in the preferences for the installed JRE's the absolute path is given and so the symlink is actually not used. I never had a problems with different JDKS under /opt/ and symlinking to my actual one. I also think that I've had several JDK's (1.5.X, 1.6.X) as installed JRE's some time ago in (an older) Eclipse and never had such problems. I also added JDK 1.6.0_7 and everything was as expected, for the execution environments I can choose between 1.6.0_18 and 1.6.0_7
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
