Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360281 - Eclipse's Proxy Settings doesn't detect Native config
Summary: Eclipse's Proxy Settings doesn't detect Native config
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-07 16:25 EDT by Marcos Cunha CLA
Modified: 2019-11-27 06:59 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos Cunha CLA 2011-10-07 16:25:56 EDT
Build Identifier: M20110909-1335

Depending on where you start Eclipse, outside or inside the main directory, it doesn't load the proper systemwide proxy configuration, so-called "Native" option on the Network Connections option, on the Preferences window.

Reproducible: Always

Steps to Reproduce:
1. Extract any Eclipse 3.7.1 on your home dir (~)
2. Open a console
3. Navigate to ~/eclipse
4. Do './eclipse', it will run normally
5. Go to "Window > Preferences", "General > Network Connections"
6. There will be the Native configuration, if your system has such proxy configured.
7. Navigate to ~ or another directory
8. Call eclipse from such path
9. In the same window, the configuration will not be displayed.
Comment 1 Laurie Green CLA 2012-04-16 08:15:41 EDT
Out of interest, how are you configuring the systemwide proxy?
Comment 2 Szymon Ptaszkiewicz CLA 2012-12-10 09:54:08 EST
Moving to Platform/Team for comment.
Comment 3 Lars Vogel CLA 2019-11-27 06:59:58 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.

If the bug is still relevant, please remove the stalebug whiteboard tag.