Default AutoUpdate site? [message #156881] |
Fri, 14 November 2003 15:38 ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: sbromley.erac.com
Currently, our company is using WSAD as our development IDE. We are trying
to come up with a strategy that would allow us to control how and when WSAD
is updated with the point releases/patches. What our company would like to
do is to bring these updates/patches internally and point our develpers to
the local versions instead of having 300+ people hitting the net at various
times and having WSAD in various updated states within our environment.
Right now, when we select the "Help->SoftwareUpdates->New Updates" selection
from the menu, the default action is to first check with the "IBM WebSphere
Studio Application Developer Discovery Site". Is there a way to override
that default discovery paths on a permanent basis? One solution is to block
the default update site in our Proxy server but that leaves me with a lot of
concerns. Pushing out a completely new build of WSAD via SMS has also been
mentioned but that has more implications that I want to address.
Any ideas/help would be appreciated. Is there an article or two out there
describing a process to keep the software updated from local resources
instead of having everyone go to the remote sites?
Thanks
Steve Bromley
Lead Software Engineer
|
|
|
Re: Default AutoUpdate site? [message #156900 is a reply to message #156881] |
Fri, 14 November 2003 16:01 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: manahan.NOSPAM.ca.ibm.com
Steve Bromley wrote:
> Currently, our company is using WSAD as our development IDE. We are trying
> to come up with a strategy that would allow us to control how and when WSAD
> is updated with the point releases/patches. What our company would like to
> do is to bring these updates/patches internally and point our develpers to
> the local versions instead of having 300+ people hitting the net at various
> times and having WSAD in various updated states within our environment.
>
> Right now, when we select the "Help->SoftwareUpdates->New Updates" selection
> from the menu, the default action is to first check with the "IBM WebSphere
> Studio Application Developer Discovery Site". Is there a way to override
> that default discovery paths on a permanent basis? One solution is to block
> the default update site in our Proxy server but that leaves me with a lot of
> concerns. Pushing out a completely new build of WSAD via SMS has also been
> mentioned but that has more implications that I want to address.
>
> Any ideas/help would be appreciated. Is there an article or two out there
> describing a process to keep the software updated from local resources
> instead of having everyone go to the remote sites?
>
> Thanks
>
> Steve Bromley
> Lead Software Engineer
>
>
You can't actually disable it with out modifying the content on each
install. Once you do that it becomes an unsupported configuration. You
can change the update sites to point to an internal one from the top
level feature.xmls. The update itself would have to be modifed as well
depending upon the type of upate it is.
Like I said however WSAD becomes unsupported once you do this. Version
3.0 of eclipse is adding support for what you are requesting but it
isn't in WSAD yet.
Peter
|
|
|
Powered by
FUDForum. Page generated in 0.03693 seconds