Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369269 - Error if starting deployment operation before system parts are initialized
Summary: Error if starting deployment operation before system parts are 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: 2012-01-20 13:23 EST by Justin Spadea CLA
Modified: 2017-02-23 14:20 EST (History)
2 users (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 Justin Spadea CLA 2012-01-20 13:23:27 EST 
This is most easily reproduced by opening a DD file, switching to the Data perspective, closing the workbench, restarting the workbench, and clicking the deploy icon from the DD's toolbar. The system parts aren't initialized (or aren't *fully* initialized), so you get a deserialization error in the deploy results view. Trying the same deploy after the system parts are initialized works fine.

This can probably be fixed by invoking ProjectEnvironmentManager.getInstance().getProjectEnvironment(sourceProject) which makes sure the parts are initialized.
Comment 1 Justin Spadea CLA 2012-02-28 15:27:35 EST 
Fixed:
RUIDeploymentModel.java
GenerateHTMLFile.java

The same problem existed in the debug code. Also fixed:
EGLLaunchableTester.java

Problem was we were initializing the environment for the source project, but not the other environments on the build path. Switched code to use ProjectEnvironment.initIREnvironments() which does what we want.
Comment 2 Justin Spadea CLA 2012-03-15 12:46:43 EDT 
Verified