André Doherty wrote:
Thank you for the hint, just tried it, eclipse standalone update
should really ease the process.
For information i used the following command (on eclipse-europa-winter) :
[PLEASE DON'T DO THIS]
Note that this affects our download statistics and we strongly
discourage our users from doing this.
As for the proxy support, i agree, eclipse and therefore the
standalone manager both make a proper use of the proxy settings i
define in my jvm (-Dhttp.proxyHost -Dhttp.proxyPort). Unfortunately
there is no way we can use it here directly.
As i was telling in my previous post, authentication on our enterprise
proxy could be very specific, not being BASIC or DIGEST or even
NTLM...., so no way any basic client can make it through it (only
internet browsers do but that involve a very "un-standard" way to
authenticate).
Can you share with us what is the product name that is used in your
infrastructure? Maybe you should open bug on Eclipse and request support
for that auth type.
That's mainly for people meeting those kind of constraints i was
suggesting that offline archive (as subclipse from tigris do for
instance).
Please see my comment above.
We may consider publishing archived site after we done with the
headless build, but for now we recommend to use the standard update manager.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
