Bug 49547 - Missing matches for static final fields inside binairy projects with attached source
Summary: Missing matches for static final fields inside binairy projects with attached...
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M7   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-05 16:35 EST by Olivier Thomann CLA
Modified: 2004-01-26 16:57 EST (History)
0 users

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 Olivier Thomann CLA 2004-01-05 16:35:03 EST 
Using M6, here is a reproducable test case.
All plugins are imported as binaries except JDT/Core + JDT/Core tests.
Go into org.eclipse.jdt.core.formatter.DefaultCodeFormatterConstants. Select for
example, FORMATTER_BLANK_LINES_BEFORE_IMPORTS and search for references in the
workspace.
It finds only two hits in the code formatter code.
It should also find a reference in the code formatter preference page code.
org.eclipse.jdt.internal.ui.preferences.formatter.BlankLinesTabPage line 86.
Comment 1 Kent Johnson CLA 2004-01-26 16:57:04 EST 
I think this has always worked this way.

We index the .class files & use their constant pool to find references, so we 
miss inlined fields. Using the attached source would be considerably slower.