Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362081 - [xtend][ui] Find references reveals ugly result
Summary: [xtend][ui] Find references reveals ugly result
Status: CLOSED FIXED
Alias: None
Product: Xtend
Classification: Tools
Component: Core (show other bugs)
Version: 2.2.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-26 10:55 EDT by Sebastian Zarnekow CLA
Modified: 2017-10-31 11:16 EDT (History)
2 users (show)

See Also:
sven.efftinge: kepler+

Attachments
Screenshot (25.98 KB, image/png)
2012-11-08 04:08 EST, Sebastian Zarnekow CLA 		no flags Details
View All 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 Sebastian Zarnekow CLA 2011-10-26 10:55:17 EDT 
Add import to org.foo.Bar to Xtend class. Find references on org.foo.Bar.
The result is displayed as <unnamed>.

It should read "import org.foo.Bar" instead.
Comment 1 Sven Efftinge CLA 2012-01-31 05:43:39 EST 
We should consider relying on JDT's find references completely, when having the trace information.
Comment 2 Sven Efftinge CLA 2012-11-08 03:55:25 EST 
Xtend reuses JDT's find references now.
Comment 3 Sebastian Zarnekow CLA 2012-11-08 04:08:32 EST 
Created attachment 223337 [details]
Screenshot

This is the search result if you do a find reference on a class that contains errors and is therefore not compiled. I'm not sure whether it qualified for 'ugly', though.
Comment 4 Eclipse Webmaster CLA 2017-10-31 11:05:00 EDT 
Requested via bug 522520.

-M.
Comment 5 Eclipse Webmaster CLA 2017-10-31 11:16:22 EDT 
Requested via bug 522520.

-M.