score:334

Accepted answer

i had the same problem. i installed eclipse 3.7 into a new folder, and created a new workspace. i launch eclipse with a -data argument to reference the new workspace.

when i attempt to connect to the marketplace to get the svn and maven plugins, i get the same issues described in op.

after a few more tries, i cleared the proxy settings for socks protocol, and i was able to connect to the marketplace.

so the solution for me was to configure the manual settings for http and https proxy, clear the settings for socks, and restart eclipse.

score:0

for me, i go to \eclipse\configuration.settings\org.eclipse.core.net.prefs set the property systemproxiesenabled to true manually and restart eclipse.

score:5

i installed handycache, in them install link on my general proxy.

in ie set proxy 127.0.0.1.

in eclipse, window > preferences > general > network connections, set active provider = native.

score:14

just to add to the thread as a possible solution, i faced a similar issue when developing on a linux system that was behind a company firewall. however, using a windows xp machine, eclipse was able to access different update sites just fine as both the manual and native network connection providers worked just fine using the company proxy.

after stumbling around for some time, i came across a discussion about using ntlmv2 and an implementation to be found at http://cntlm.sourceforge.net/. to whomever posted this, i give much credit to as it helped me get past the issue running on linux. as a side note, i was using eclipse 3.6.2 / helios on both the linux and windows distros.

best of luck on finding a solution!

score:14

finally work for me !

in eclipse, window > preferences > general > network connections,
set active provider to native
add to eclipse.ini :

-djava.net.usesystemproxies=true
-dhttp.proxyport=8080
-dhttp.proxyhost=myproxy
-dhttp.proxyuser=mydomain\myusername
-dhttp.proxypassword=mypassword
-dhttp.nonproxyhosts=localhost|127.0.0.1|192.168.*|10.*
-dorg.eclipse.ecf.provider.filetransfer.excludecontributors=org.eclipse.ecf.provider.filetransfer.httpclient4

score:15

there is an eclipse.ini (sts.ini) parameter that can help:

-djava.net.usesystemproxies=true

a lot of effort wasted on this trivial setting each time i change the work environment... see one of the related bugs on eclipse bugzilla.

score:39

manual + disable socks didn't work for me (still tried to use socks and my company proxy refused it),
native + changed eclipse.ini worked for me

-dorg.eclipse.ecf.provider.filetransfer.excludecontributors=org.eclipse.ecf.provider.filetransfer.httpclient
-dhttp.proxyhost=myproxy
-dhttp.proxyport=8080
-dhttp.proxyuser=mydomain\myusername
-dhttp.proxypassword=mypassword
-dhttp.nonproxyhosts=localhost|127.0.0.1

these settings require ide restart (sometimes with -clean -refresh command line options).
https://bugs.eclipse.org/bugs/show_bug.cgi?id=281472


java8, eclipse neon3, slow proxy server:

-dorg.eclipse.ecf.provider.filetransfer.excludecontributors=org.eclipse.ecf.provider.filetransfer.httpclient4
-dhttp.proxyhost=<proxy>
-dhttp.proxyport=8080
-dhttps.proxyhost=<proxy>
-dhttps.proxyport=8080
-dsocksproxyhost=
-dsocksproxyport=
-dhttp.proxyuser=<user>
-dhttp.proxypassword=<pass>
-dhttp.nonproxyhosts=localhost|127.0.0.1
-dorg.eclipse.equinox.p2.transport.ecf.retry=5
-dorg.eclipse.ecf.provider.filetransfer.retrieve.connecttimeout=15000
-dorg.eclipse.ecf.provider.filetransfer.retrieve.readtimeout=1000
-dorg.eclipse.ecf.provider.filetransfer.retrieve.retryattempts=20
-dorg.eclipse.ecf.provider.filetransfer.retrieve.closetimeout=1000
-dorg.eclipse.ecf.provider.filetransfer.browse.connecttimeout=3000
-dorg.eclipse.ecf.provider.filetransfer.browse.readtimeout=1000

Related Query

More Query from same tag