Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 184598 - Centralised proxy settings in Eclipse 3.3
Summary: Centralised proxy settings in Eclipse 3.3
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Geclipse (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Mathias Stümpert CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 185110
  Show dependency tree
 
Reported: 2007-04-28 08:40 EDT by Markus Knauer CLA
Modified: 2014-01-09 16:18 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 Markus Knauer CLA 2007-04-28 08:40:00 EDT 
In Eclipse 3.2 every component like Update Manager, g-Eclipse, ... had its own preference settings for proxies. This information is available from a centralized place in Eclipse 3.3.

When we switch to Eclipse 3.3 builds we should remove our own proxy settings page and use the centralized information.

See 'Platform level proxy and SSH2 settings' in the New & Noteworthy document of Eclipse 3.3.
Comment 1 Mathias Stümpert CLA 2007-05-04 07:00:04 EDT 
The g-Eclipse network preference page and all related preferences have vanished. The core itself now uses the Eclipse 3.3 proxy settings.
Comment 2 Mathias Stümpert CLA 2007-05-31 07:40:13 EDT 
closing this ticket