Bug 225287 - Support source lookup path/context for stack trace console
Summary: Support source lookup path/context for stack trace console
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-02 05:29 EDT by Clemens Fuchs CLA
Modified: 2009-02-19 19:06 EST (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Clemens Fuchs CLA 2008-04-02 05:29:21 EDT 
Build ID: I20070621-1340

Steps To Reproduce:
1. I have several projects in my workspace, which have same classes (-> several release branches of our product)
2. paste a text into the stack trace console
3. click a hyperlink

-> the corresponding class of the first project is opened, but i wanted it to open the class in the second project.
Therefore I created and activated a working set, which only shows the second project (Java Browsing View)


More information:
Comment 1 Martin Aeschlimann CLA 2008-04-21 17:06:06 EDT 
Console is in Debug.
Comment 2 Darin Wright CLA 2008-04-21 23:12:14 EDT 
Not much we can do about this. The stack trace console uses the entire workspace when searching for classes - a stack trace within a console associated with a launch config will use the search lookup path assocaited with that launch config. If we have no context, we can't do much better thana global search - and the first hit wins.

The only thing we could do is allow the user to set a context (launch config).
Comment 3 Clemens Fuchs CLA 2008-04-22 02:44:23 EDT 
From user point of view I'd expect to set a context for the stack trace console (e.g. project, working set, launch config)
Comment 4 Darin Wright CLA 2008-04-22 09:17:14 EDT 
marking as assigned for future consideration