Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 23030 - Compilation with external name lookup
Summary: Compilation with external name lookup
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 22834
  Show dependency tree
 
Reported: 2002-08-30 10:05 EDT by Darin Wright CLA
Modified: 2009-08-30 02:37 EDT (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 Darin Wright CLA 2002-08-30 10:05:33 EDT 
The debugger would benefit from the ability to perform compilation of snippets 
without the context of an IJavaProject. This would support expression 
evaluation when a project context is not available (stand alone debugging). We 
require a way to supply an "INameEnvironment", to assist in the compilation. On 
first glance this looks like it would be a big request, as the objects returned 
by the name environment are all internal types. Investigation appreciated.
Comment 1 Philipe Mulet CLA 2002-09-02 07:32:16 EDT 
As said, this would commit us to surface quite a number of internal entities, 
along with some implementations of these I presume to make it more useful 
(builder environment, searchable environment, ...). Unclear we want to commit 
to these.

Maybe a separate approach for only feeding a custom classpath would be all you 
need ?
Comment 2 Philipe Mulet CLA 2002-10-28 08:45:54 EST 
May reconsider if moving towards compiler API. Post 2.1
Comment 3 Eclipse Webmaster CLA 2009-08-30 02:37:42 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.