Community
Participate
Working Groups
Currently each feature defines its own update site. To reduce network traffic inside a network with more than 100 Eclipse installations it would be nice if Eclipse would have an build-in option to _force_ a fixed update site that overwrites the update site of all installed features. This would also allow us to test new plugins before releasing them to our teams. Currently we have to workaround this by having our internal DNS resolving "updates.eclipse.org" to an internal IP (wich is a mirror of the Eclipse update site).
See bug 37702 comment #4 *** This bug has been marked as a duplicate of 37702 ***