Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 313681 - PDE does not complain about unsuccessful synchronization between .product and plugin.xml
Summary: PDE does not complain about unsuccessful synchronization between .product and...
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-20 05:30 EDT by Kai Toedter CLA
Modified: 2019-09-09 02:31 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Toedter CLA 2010-05-20 05:30:11 EDT
I had the following use case; After unzipping a RCP project and launching it, I got a runtime exception regarding not existing product properties (Window images). But they where defined correctly in the .product file. Even manually pressing "Synchronize" in the product configuration editor did not help. I found out that the synchronization did not happen because the corresponding plugin.xml was "read only" (I don't know why but this does not matter here :)

After making the whole project "read/write" manually everything worked correctly.

It would have helped me tremendously if Eclipse would have warned me that a required synchronization failed.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:04:44 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 2 Julian Honnen CLA 2019-09-09 02:31:16 EDT
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.