Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370200 - Capture trace information
Summary: Capture trace information
Status: CLOSED FIXED
Alias: None
Product: Xtend
Classification: Tools
Component: Core (show other bugs)
Version: 2.3.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: M7   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-31 06:23 EST by Sven Efftinge CLA
Modified: 2017-10-31 11:18 EDT (History)
2 users (show)

See Also:
sven.efftinge: juno+

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 Sven Efftinge CLA 2012-01-31 06:23:23 EST 
We need to capture the trace information from source code to the generated Java files. This can be used for all kinds of things. One is a tighter integration with Java Development Tools.
Comment 1 Sebastian Zarnekow CLA 2012-02-14 05:47:17 EST 
Committed first shot to master.
Comment 2 Knut Wannheden CLA 2012-03-09 02:22:56 EST 
Don't know if this is the right place to report this. If I have an expression like "new Bar().bar" and then open the call hierarchy for Bar#bar() then the selected text will be "new Bar().bar" instead of just "bar".
Comment 3 Sebastian Zarnekow CLA 2012-03-09 06:19:02 EST 
Thanks for the hint, Knut. Obviously there are not enough tests for the simple cases ;-)
Comment 4 Sebastian Zarnekow CLA 2012-04-26 05:06:20 EDT 
I think we can close this one and track remaining problems in more concrete issues.
Comment 5 Eclipse Webmaster CLA 2017-10-31 11:07:28 EDT 
Requested via bug 522520.

-M.
Comment 6 Eclipse Webmaster CLA 2017-10-31 11:18:53 EDT 
Requested via bug 522520.

-M.