Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344147 - product configuration settings not carried through at launch
Summary: product configuration settings not carried through at launch
Status: RESOLVED WORKSFORME
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-28 11:30 EDT by Jeff McAffer CLA
Modified: 2019-09-02 14:55 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 Jeff McAffer CLA 2011-04-28 11:30:08 EDT
in m7

This looks like a regression as I'm sure this worked before...

- create a dummy .product configuration
- On the Configuration tab add some properties
- launch the product
- look at the generated launch configuration and the resultant disk structure  under <workspace>/.metadata/.plugins/org.eclipse.pde.core/<your>.product and notice that your properties are not mentioned anywhere.

This is a pretty significant problem as it makes using the Properties settings hard to test.

Please consider for Indigo if the fix is not too risky.
Comment 1 Eclipse Genie CLA 2018-11-14 19:03:19 EST
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.

--
The automated Eclipse Genie.
Comment 2 Lars Vogel CLA 2019-09-02 14:55:23 EDT
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.