Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352007 - Dependent project's IR environment not always initialized
Summary: Dependent project's IR environment not always initialized
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Justin Spadea CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 13:42 EDT by Justin Spadea CLA
Modified: 2017-02-23 14:18 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 Justin Spadea CLA 2011-07-13 13:42:32 EDT 
If A depends on B, and you make a change in a file in A before you've built anything in B, then B's IR environment won't have run its initialization and you'll get errors trying to deserialize anything from B when compiling something from A.
Comment 1 Justin Spadea CLA 2011-07-13 13:52:45 EDT 
Fixed ProjectEnvironmentManager.java, ProjectEnvironment.java, and ProjectBuildPathEntry.java. Instead of just initializing the IR environment for the project being built, we initialize the IR environments for the project's entire build path.
Comment 2 Justin Spadea CLA 2011-09-08 14:19:58 EDT 
Verified