Bug 273295

Summary: ReferenceAnalyzer needs to handle different search scopes
Product: [Eclipse Project] PDE Reporter: Michael Rennie <Michael_Rennie>
Component: API ToolsAssignee: Michael Rennie <Michael_Rennie>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: P3 CC: darin.eclipse
Version: 3.5Keywords: performance
Target Milestone: 3.6   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Bug Depends on:    
Bug Blocks: 233643    

Description Michael Rennie CLA 2009-04-22 12:03:25 EDT 
FUP to bug 271684

Our ReferenceAnalyzer needs some refactoring to be able to specify what types are passed to the different kinds of usage scanning. This is needed so that we do not scan too many types for the leak usage checks which do not care about dependent types. With separate analysis we could also leverage meta-data about API description changes to know if the normal usage scan should be a no-op.

A first step would be to have the analyzer accept a build context instead of a search scope, that way the analyzer could created scopes as it sees fit and pass them to the various scans.
Comment 1 Michael Rennie CLA 2009-05-06 11:37:25 EDT 
moving to 3.6 as the partial solution so far is too large for an RC fix this late in the game
Comment 2 Michael Rennie CLA 2009-11-30 10:32:44 EST 
Depending on the performance impact from bug 296482, this will be invalid.
Comment 3 Michael Rennie CLA 2010-03-25 10:19:22 EDT 
this bug is no longer valid as we now compute CRCs to detect if we should perform use scans or not - and our BuildContext has been optimized with the fix for bug 233643