Community
Participate
Working Groups
i get a stacktrace which goes into a JAR not part of the project nor in its build path. click on the "(classname.java:line)" link tries to find the JAR elsewhere, taking whatever it finds in the workspace. i have to close all projects possibly containing a version of the JAR in their build paths to finally get a "Source not found for ....". it is apparently impossible to influence JDT in its arbitrary decisions and even if it fails, it does not offer a way to select the JAR on my own. having to close other projects, which are in no way related or connected to the current project, just because JDT fails to accept that it doesn't know what it does, is inacceptable -- and that even when it finally gives up it does not offer a way for me to finally tell it how wrong it is and where to look instead, even more.
Can you please provide reproducible steps.
- create several jars with the same class - distribute over several open projects in workspace - use a project that by name or creation date is in the middle of all those projects (since i don't know why eclipse choses the worng prject/jar, i cannot be more specfic) - create stacktrace that involves the class from the jar - click the stacktrace's "(classname.java:line)" part - find yourself in the wrong project/jar
*** Bug 433315 has been marked as a duplicate of this bug. ***
(In reply to arne anka from comment #2) > - create several jars with the same class > - distribute over several open projects in workspace > - use a project that by name or creation date is in the middle of all those > projects (since i don't know why eclipse choses the worng prject/jar, i > cannot be more specfic) > - create stacktrace that involves the class from the jar > - click the stacktrace's "(classname.java:line)" part > - find yourself in the wrong project/jar Can you attach a sample workspace, I tried with exporting to 5 different jars.
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.
Can not reproduce. Please reopen and provide workspace if you still see the issue.
I cannot provide a workspace of several GB and with commercial projects in it. From current experiences with - Java Stacktrace Console - Junit view I confidently can say that the source lookup a) takes the first source file matching package and class name in the workspace b) does not check the originating project's class path to make sure whether that source file's location is actually part of it If you cannot reproduce, it may happen only in large workspaces with many files and projects? OTOH I've experienced that issue over the years in at least 4 completely unrelated workspaces and Eclipse installations. Can you give me some pointers as to where to enable logging for the lookup or where to start debugging the code flow in JDT?
Forgot another bit of damning evidence: the momnent I close the "competing" project, source lookup stays on the straight and narrow.
Nothing changed. Issue persists.
