|
| Re: Best way to test an update site [message #334514 is a reply to message #334480] |
Fri, 13 February 2009 16:04  |
Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 2/11/2009 7:38 PM, Konstantin Komissarchik wrote:
> I am wondering if people have a recommendation or a best practice for
> the best way to test an update site prior to publishing the content to
> the actual live pubic server. I can easily test making a new install by
> simply pointing to a local update site, but I haven't been able to
> figure out how to test detection and application of an update to an
> existing installation. The features in the existing installation have an
> update site reference to our public update site, so they will go looking
> updates there. I guess what we need is a way to tell the update manager
> / p2 that when it sees a certain update site url, it should use a
> different one instead. Does something like this exist? Is there another
> approach that people would recommend for this situation?
So-called policy files can probably help:
http://wiki.eclipse.org/Using_Policy_Files#Usage
Hope this helps,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.03624 seconds
] 
Search
Help
Register
Login
Home
