Community
Participate
Working Groups
I20080422 1. Have org.eclipse.jdt.compiler.tool v_854 in your dev workspace 2. Start a runtime workbench 3. Load org.eclipse.jdt.ui v20080422-0800 from CVS 4. Open type org.eclipse.jdt.internal.compiler.tool.Archive.class Observe: No source is displayed for this type
Created attachment 97424 [details] Proposed fix and regression test
Fix and test released for 3.4M7
The initial scenario does not work indeed, but the test case of comment #1 works. Discussed with Jérôme and opened bug 229304 for the scenario breakage, which is not source-attachment related. A validation scenario that would work is the following: 1. Have org.eclipse.jdt.compiler.tool v_854 in your dev workspace 2. Start a runtime workbench (further steps all use that workbench) 3. Load org.eclipse.jdt.ui v20080422-0800 from CVS 4. Expand its Plug-in Dependencies 5. In the Package Explorer, drill down upon 'bin [path depends on your disk layout]/org.eclipse.jdt.internal.compiler.tool/Archive.class' file 6. Double-click on it Expected: an editor opens upon its attached source. Result using org.eclipse.jdt.core dated 20080422: a class file editor opens instead. I20080427-2000 behaves as expected, hence: Verified for 3.4 M7 using build I20080427-2000.