Community
Participate
Working Groups
Build Identifier: Similar to bug 346116, If the class files (with no source) are in a jar on the build path, but the source is only added to the source lookup path, inspect from the editor will fail, the .java file is opened. -If the class file is on the build path, but the source is made available by using the "attach source action" in the class file editor, inspect succeeds and the .class file is opened. If the source is made available using "attach source" and the same jar is on the source lookup path, inspect will still not work. The Reproducible: Always Steps to Reproduce: Reuse the testcase from bug 346116, but slightly modified: The setup: There are 2 projects, JavaPrj (a Java project) contains my code and it makes use of a class inside of jar. The jar is located inside of SimplePrj\lib (a simple project). The jar contains ONLY the binary code. Another jar contains the source - util_src.jar. JavaPrj makes a reference to the jar through the Java Build Path -> Libraries > Add Jars... button The Run: (using the attach testcase) - Add a breakpoint to RunMe.java at the initUtil method. - Debug the application - When the Eclipse stops at the breakpoint step inside of u.putAttributes - Once inside try to inspect 'this'
Created attachment 203456 [details] testcase
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.
