Community
Participate
Working Groups
tested with 20020502 latest workspace: 1) Make sure JRE_SRC is empty. 2) Create a Java project. 3) Open properties page on the rt.jar of the project. 4) Create a new variable JRE_TEST_SRC and set it to some valid src.jar 5) Open a class file in the rt.jar. 6) Observe that the editor remains empty. This blocks me to fully test a feature in M6: bug 13581
This seems not be specific to rt.jar. I just tried to detach a valid source (bootsrc.zip from boot.jar in org.eclipse.core.boot) and to reattach it. The source stays detached.
This works for me in build 20020508. For rt.jar, I had to make sure that the root path was not empty (this was not specified in the steps you gave). For boot.jar, I was able to detach then reattach its source and then open a class and see its source.
I tried it in 20020508 on w2k: Attaching seems to work now (tried with boot.jar) but when I detach, the sources are remembered. 1) Open VM.class from org.eclipse.core.boot. 2) Verify that you can see the source. 3) Close VM.class and remove the source attachment from boot.jar 4) Open VM class again. 5) Observe that the source is visible.
On linux-motif 20020508, attaching/detaching seems to work.
with 20020514-I and jdt.core patch on w2k and Linux-Motif: SWT sources cannot be found (IClassFile.getSourceRange() always returns null). However, with other jars like org.eclipse.boot/boot.jar or rt.jar, it works. I suspect it must have to do with the specific location of the jar and/or the source of SWT.
No, the problem is the swt classes were compiled without the source attribute.
Closing