Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332157 - API Use Scan builder places markers incorrectly for inner types
Summary: API Use Scan builder places markers incorrectly for inner types
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: API Tools (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P4 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE API Tools Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 331996
Blocks:
  Show dependency tree
 
Reported: 2010-12-08 12:29 EST by Curtis Windatt CLA
Modified: 2019-05-02 08:39 EDT (History)
3 users (show)

See Also:

Attachments
WIP (5.77 KB, patch)
2010-12-08 13:57 EST, Curtis Windatt CLA 		no flags Details | Diff
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 Curtis Windatt CLA 2010-12-08 12:29:28 EST 
+++ This bug was initially created as a clone of Bug #331996 +++

The API Use Scan builder doesn't handle correct marker placement when dealing with inner types and nested inner types.
Comment 1 Curtis Windatt CLA 2010-12-08 13:57:10 EST 
Created attachment 184806 [details]
WIP

Combination of Mike's patch, a couple tweaks and a new test.  Still needs some work.
Comment 2 Michael Rennie CLA 2011-04-18 12:04:02 EDT 
If I am recalling correctly, the problem is for:

1. inner types
2. nested inner types
3. anonymous types
4. local types
Comment 3 Michael Rennie CLA 2011-04-18 12:09:36 EDT 
We have all of the code to correctly place problem markers in our problem detector framework, see AbstractProblemDetector#getSourceRange(..) and subclasses for examples.
Comment 4 Curtis Windatt CLA 2011-04-18 16:09:29 EDT 
Not a high priority as the marker does get created (just not on the correct line).  We will look at this in the RC builds if there is time.
Comment 5 Eclipse Genie CLA 2019-05-02 08:39:24 EDT 
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.