Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350094 - Working Copy Compiler should push the current ProjectIREnvironment on the Environment stack
Summary: Working Copy Compiler should push the current ProjectIREnvironment on the Env...
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Justin Spadea CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 350092
Blocks:
  Show dependency tree
 
Reported: 2011-06-22 15:22 EDT by Paul Harmon CLA
Modified: 2017-02-23 14:14 EST (History)
1 user (show)

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 Paul Harmon CLA 2011-06-22 15:22:09 EDT 
Currently the WCC does not push it's environment onto the Environment stack. This is working fine for now, because the WCC always gets bindings from source (instead of reading IRs and converting them to bindings via Mof2Binding). However, when we start adding EGLARs into EDT, this will cause a problem, because bindings from EGLARs can only be converted via Mof2Binding. Mof2Binding has several places where it uses Environment.getCurrentEnv() to find things like system parts.

This Bug should not be fixed until Bug 350092 is fixed, because pushing the extra environment could cause problems if the builder is running.
Comment 1 Justin Spadea CLA 2011-07-06 17:42:15 EDT 
Fixed WorkingCopyProcessingQueue.java and WorkingCopyCompiler.java
Comment 2 Paul Harmon CLA 2011-10-24 08:57:12 EDT 
good