Summary: | [Net] Default preference gets ignored | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Markus Kuppe <bugs.eclipse.org> | ||||||
Component: | Team | Assignee: | Wojciech Galanciak <wojciech.galanciak> | ||||||
Status: | RESOLVED FIXED | QA Contact: | |||||||
Severity: | normal | ||||||||
Priority: | P3 | CC: | daniel_megert, remy.suen, Szymon.Brandys, tomasz.zarna, wojciech.galanciak | ||||||
Version: | 3.4 | Flags: | Szymon.Brandys:
review+
|
||||||
Target Milestone: | 3.7 M3 | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
Attachments: |
|
Description
Markus Kuppe
2008-07-25 05:55:50 EDT
The proxy preferences from plugin_customisation.ini doesn't get load because ProxyManager looks for settings directly in a configuration scope node. For this facility to work also default scope has to be searched. I will provide a patch as soon as I come up with a proper solution. The change appeared to be more complex since there is code that explicitly walks through configuration scope nodes. No time to address the issue right now. Maybe someone is willing to help... Created attachment 179635 [details] patch This patch provides support for default values of proxy preferences. Main features: - possibility to provide default settings through -pluginCustomization which allows to use proxy settings in headless mode, - separation of direct operations on preferences to PreferencesManager - interaction with preferences only by using its public methods - ability to get default values of proxy settings for e.g. full functional Restore Defaults button (bug 283036). Created attachment 180349 [details]
updated patch
Now it looks good. Thanks Wojtek. This fix is not good. It causes exceptions, see bug 327672. |