Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Resource .buckminster/tp is not local
Resource .buckminster/tp is not local [message #630347] Fri, 01 October 2010 12:32
Thorsten Meinl is currently offline Thorsten Meinl
Messages: 85
Registered: July 2009
Member
Hi all,

This error message is bugging our team for quite some time. It occurs if
you want to refresh the Buckminster meta-data and leads to
missing/old/outdated meta-data because refreshing does not take place
after all.
Since this problem does not occur in all cases I tried to track it down
and one possible explanation is the following:
The error message (in fact an exception that stops the refresh process)
is caused because Eclipse has not yet fully scanned the
..buckminster-project that contains the target platform. It is considered
as non-local and certain operations performed during meta-data refresh
(starting in WorkspaceInfo.forceRefreshOnAll) can only be performed on
local ressources (get/setPersistentProperty). The problem can be solved
by starting Eclipse once with '-refresh' so that also the hidden
..buckminster project is fully scanned and recognized as local. Usually
this should happen right after the materialization process but I have
the feeling that workspace refresh and meta-data refresh are interfering
i.e. meta-data refresh starts before the workspace refresh has finished.
This is substantiated by the observation that for few materialized
projects there are almost no problems but for many materialized
components the problem occurs every time.
Maybe you could have a look into that.

Cheers,

Thorsten
Previous Topic:Adding source feature causes MissingComponentException in site.p2.zip action
Next Topic:Buckminster cvs materializing, uses a proxy, how is this configured?
Goto Forum:
  


Current Time: Thu Aug 21 04:15:22 EDT 2014

Powered by FUDForum. Page generated in 0.02222 seconds