OK, so a simple reboot their IDE would actually suffice in that case.
I'll convey that and ask if that can be the case.
Thanks,
- thomas
On 03/19/2010 09:06 PM, John Arthorne wrote:
The only thing that comes to mind is that p2 caches
repositories in memory for brief periods (using soft references). If
the repository on the server is updated, the client won't see it while
the repository is cached in memory. However, these caches are
short-lived, and every time a repository is loaded from local disk
cache it does a timestamp comparison with the contents on the server.
So, as long as your server timestamps are changing the client should be
picking up the new contents very soon. I suppose if somebody is holding
onto IRepository instances for longer periods, it will prevent the
SoftReference being cleared and the stale repository might be seen for
longer periods.
John
On Fri, Mar 19, 2010 at 12:29 PM, Thomas
Hallgren <thomas@xxxxxxx> wrote:
Hi,
I got the question below from a client. Is there anything he can do to
make absolutely sure that his users finds the updated features? I seem
to recall that there was some issue with this, but I don't seem to find
it.
Thanks,
- thomas
-------- Original Message --------
Hi
Thomas,
I
recently updated the internal 3.5 mega repo to 3.5.2. Since doing this
a few people have been getting the "No repository found containing..."
error when trying to install new stuff from the mega repo. The solution
to this is as follows:
- Make
sure
you are up to date by reloading the mega repo:
- Window
>
Preferences > Install/Update > Available Software sites
- Select
the
3.5 mega repo and press the Test Connection button
- Press
OK
- Help
>
Check for updates
- Install
all
updates found and restart
- Try
installing
the new stuff again.
It looks like eclipse 3.5
is
not, in some cases, noticing when our internal repos are updated and re-downloading
the metadata. There is therefore a mismatch between
what's in meta cached by the IDE and
what's in the repo. (I have just verified that this is the case. The
missing artifacts are all in the previous release.) Do you know what we
can do to ensure that eclipse notices that repo metadata needs
refreshing?
Thanks,
Miles
Miles Daffin
Morgan
Stanley | IDEAS Practice Areas
25
Cabot
Square | Canary Wharf | Floor 03
London, E14 4QA
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
|
