A way to disable automatic update?

buildship

(Willie) #1

the core eclipse site is blocked by our firewall. I just noticed hundreds of this

!ENTRY org.eclipse.equinox.p2.transport.ecf 4 1002 2017-01-30 10:32:08.880
!MESSAGE Unable to read repository at http://download.eclipse.org/buildship/updates/e45/milestones/2.x/compositeContent.xml.
!STACK 0
org.apache.http.NoHttpResponseException: download.eclipse.org failed to respond
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143)
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
	at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:260)
	at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:283)
	at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:251)
	at org.apache.http.impl.conn.ManagedClientConnectionImpl.receiveResponseHeader(ManagedClientConnectionImpl.java:197)
	at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:271)
	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
	at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:685)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:487)
	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
	at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientFileSystemBrowser.runRequest(HttpClientFileSystemBrowser.java:259)
	at org.eclipse.ecf.provider.filetransfer.browse.AbstractFileSystemBrowser$DirectoryJob.run(AbstractFileSystemBrowser.java:69)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

I’m not sure if this is a buildship thing or an eclipse thing, but if its a buildship thing, its probably a good idea to make this switchable. Our infrastructure is setup where the only eclipse plugins that can be installed come thru our internal marketplace server. all access to eclipse.org are blocked.

Reason this is an issue, is our security team is installing tools that will notify HR of internet usage violations. If this thing keeps pounding its head against the firewall every day, there’s a chance a dev can be reported to HR for a violation when they had no idea they were committing one.


(Donát Csikós) #2

This is probably caused by the platform’s update functionality. By default - afaik - it is turned on, but you can deactivate it any time.

Another thing you can do, you can delete/disable the urls at the ‘Available Software Sites’ section of the preferences, so that Eclipse won’t be able to access any update sites.