| Summary: | Configuration properties deleted when file edited. | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Matthew Dickie <m.dickie> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | curtis.windatt.public |
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
This was fixed/added in 3.7 M2. *** This bug has been marked as a duplicate of bug 260328 *** |
Build Identifier: I20100608-0911 I found (from a post to the org.eclipse.rcp platform by Andrew Niefer, subject: 'Re: .procuct editor and option for config.ini file', date: 20/07/2009 15:35) that you can specify properties to go into the config.ini file in the .product file, even though the UI doesn't support it. I use this in the following way: <configurations> <property name="osgi.instance.area.default" value="@user.home/workspace"/> </configurations> Note that this property element is the only child of the configurations element, I don't set any start levels for any of the bundles. The problem (despite the UI not supporting this, and it being undocumented) is that whenever I make the slightest change to the product using the UI (for example to move the location of the progress bar during start-up), this element is deleted. Reproducible: Always Steps to Reproduce: 1. Create a new product configuration file. 2. Open the product configuration file in a text or xml editor and add the following: <configurations> <property name="osgi.instance.area.default" value="@user.home/workspace"/> </configurations> 3. Open the product configuration file in the product configuration file editor and make any change. The configurations element and its child property element will be deleted.