Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326589

Summary: Reloading target platform causes target bundles to go missing
Product: [Eclipse Project] PDE Reporter: Bryan Hunt <bhunt>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: curtis.windatt.public, jeffmcaffer
Version: 3.6.1   
Target Milestone: 3.7   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Bryan Hunt CLA 2010-09-29 15:43:09 EDT 
We ran into a case where we updated the target platform on a machine and when we reloaded the target platform from the UI, most of the bundles in the target were not "found" which caused build to fail.  I've given Curtis the workspace and target platform for further investigation.
Comment 1 Curtis Windatt CLA 2010-09-29 15:52:16 EDT 
I will continue to do some investigating.  People have reported errors like this occasionally, where restarting Eclipse fixes things.

What I know so far:
The target definition resolves correctly (all bundles are downloaded and available).
The preferences are storing the correct values (and are loaded correctly at startup).
The problem only occurs when reloading the target.

The problem must occur somewhere around the LoadTargetDefinitionJob.  There we create a state using urls from the target definition vs at startup where we get them from the preferences.  The resulting state contains no bundles from the target, so it is failing completely.  However, it doesn't seem to have anything to do with the contents of the target as recreating the target in another workspace makes things work again.
Comment 2 Curtis Windatt CLA 2010-10-07 15:43:45 EDT 
I have been unable to reproduce using a copy of the workspace that was causing the problem.  We also have seen the opposite problem (reloading works but restarting fails) in bug 327136.
Comment 3 Curtis Windatt CLA 2010-10-18 15:26:22 EDT 
Removing milestone, it doesn't look like we'll be able to do anything about this at this time.  I have been unable to reproduce and the problem is transient (using the same target on different workspaces or machines works correctly).
Comment 4 Curtis Windatt CLA 2011-01-31 14:37:57 EST 
Closing as WORKSFORME.  We haven't been able to reproduce enough to have any idea what the cause is.