|
| Re: [p2] always contacting update-site when installing feature [message #332086 is a reply to message #332020] |
Thu, 02 October 2008 13:09   |
 Beth Tibbitts
Messages: 231
Registered: July 2009 |
Senior Member |
|
|
I am seeing a similar thing with 3.4 updates.
We distribute a PTP build via an archived update site, and when the user
uses a CDT (a pre-req) update site via another archive, it still uses
the network to download things that should be available in the archived
update site on the local machine.
What gives?
When users don't have network access, I too see hangs. When their access
is slow, it's excruciating. That's why I gave them archive update
sites, so they wouldn't have to wait on the network!
Beth Tibbitts
http://eclipse.org/ptp
Carsten Pfeiffer wrote:
> Hi,
>
> we're distributing an archived update-site of our product that includes some
> Eclipse-features (namely GEF). The GEF-Feature is unmodified and thus
> includes
>
> <url>
> <update label="%updateSiteName"
> url=" http://download.eclipse.org/tools/gef/update-site/releases/s ite.xml"/>
> <discovery label="%updateSiteName"
> url=" http://download.eclipse.org/tools/gef/update-site/releases/s ite.xml"/>
> </url>
>
> in the feature.xml.
>
> Now when trying to install our archived site, the installation hangs when no
> network is available. p2 is obviously trying to contact the GEF update
> site, even though the feature is completely available in the archived site.
>
> Even more, when the network is available, p2 decides to install a newer
> version of GEF (3.4.1) than the one shipped with our archived update site
> (3.4.0). IMHO this is a bit too much magic.
>
> Should we remove those <url> entries from the feature? Or what's the
> preferred way to do this?
>
> (This is with Eclipse 3.4.1)
>
> Thanks,
> Carsten
|
|
|
|
| Re: [p2] always contacting update-site when installing feature [message #332316 is a reply to message #332128] |
Fri, 17 October 2008 21:33 |
Beth Tibbitts
Messages: 231
Registered: July 2009 |
Senior Member |
|
|
That bug was marked as a duplicate of:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=235923
And from reading through the (long) discussion, it appears to be the
same thing I'm seeing: When updating from local jar files, it still goes
to the network to find things it shouldn't bother with.
And there doesn't seem to be a resolution either.
....Beth
Carsten Pfeiffer wrote:
> Beth Tibbitts wrote:
>
> Thanks for the comments, Beth.
>
> I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=249753 for this.
>
> Cheers,
> Carsten
>
>> I am seeing a similar thing with 3.4 updates.
>> We distribute a PTP build via an archived update site, and when the user
>> uses a CDT (a pre-req) update site via another archive, it still uses
>> the network to download things that should be available in the archived
>> update site on the local machine.
>> What gives?
>> When users don't have network access, I too see hangs. When their access
>> is slow, it's excruciating. That's why I gave them archive update
>> sites, so they wouldn't have to wait on the network!
>>
>> Beth Tibbitts
>> http://eclipse.org/ptp
>
|
|
|
Powered by
FUDForum. Page generated in 0.03367 seconds
] 
Search
Help
Register
Login
Home
