Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369764 - [documentation] Document importproxysettings command
Summary: [documentation] Document importproxysettings command
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Buckminster (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: buckminster.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 369695
Blocks:
  Show dependency tree
 
Reported: 2012-01-25 20:15 EST by Michal Ruzicka CLA
Modified: 2019-02-25 14:41 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Ruzicka CLA 2012-01-25 20:15:17 EST 
+++ This bug was initially created as a clone of Bug #369695 +++

The importproxysettings command mirrors proxy settings defined in system properties (if any) to eclipse/workspace preferences. Ensuring that the two are in sync and as a result preventing undesired effects that may otherwise be observed, like for instance overriding the system properties defining the proxy settings by the Platform Proxy API code in an effort to make the proxy information in the system properties match the information in the eclipse/workspace preferences.
The command must be executed before the Platform Proxy API code is initialized (before the 'org.eclipse.core.net' bundle is started) in order to be able to process the system properties defining the proxy settings before they are potentially overridden by the Platform Proxy API code. So it is crucial to execute it as one of the first commands (the very first if possible) in buckminster scripts.