Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » ERROR: Could not read metadata (Buckminster workspace setup throws errors)
ERROR: Could not read metadata [message #558762] Tue, 14 September 2010 11:15 Go to next message
Tomsen  is currently offline Tomsen
Messages: 42
Registered: July 2010
Member
Hi,
in my buckminster step I get these errors when doing the buckminster step:
Gestartet durch Benutzer anonymous
Updating https://80.77.17.181/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.softproject.xe.standalone.releng
At revision 29307
no change for https://80.77.17.181/svn/MAIN/Products/Eclipse-RCP/XSLEasy/trunk/de.softproject.xe.standalone.releng since the previous build
[workspace] $ /bin/sh -xe /tmp/tomcat6-tmp/hudson8381369816374160784.sh
+ rm -Rf /build/hudson/jobs/xslEasy40/workspace/buckminster.output
+ rm -Rf /build/hudson/jobs/xslEasy40/workspace/buckminster.temp
+ rm -Rf /build/hudson/jobs/xslEasy40/workspace/features
+ rm -Rf /build/hudson/jobs/xslEasy40/workspace/plugins
+ ls /build/hudson/jobs/xslEasy40/workspace
[workspace] $ /usr/lib/jvm/java-6-sun/bin/java -Dbuckminster.output.root=/build/hudson/jobs/xslEasy40/workspace/buckminster.output -Dbuckminster.temp.root=/build/hudson/jobs/xslEasy40/workspace/buckminster.temp -Xmx256m -jar /build/hudson/tools/Bucky_3.6_Subversive/buckminster/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar -application org.eclipse.buckminster.cmdline.headless -data /build/hudson/jobs/xslEasy40/workspace --loglevel info -S /build/hudson/jobs/xslEasy40/workspace/commands.txt
ERROR: Workspace restored, but some problems occurred.
  ERROR: Could not read metadata for 'de.softproject.common'.
org.eclipse.core.internal.resources.ResourceException: The project description file (.project) for 'de.softproject.common' is missing.  This file contains important information about the project.  The project will not function properly until this file is restored.
	at org.eclipse.core.internal.localstore.FileSystemResourceManager.read(FileSystemResourceManager.java:756)
	at org.eclipse.core.internal.resources.SaveManager.restoreMetaInfo(SaveManager.java:852)
	at org.eclipse.core.internal.resources.SaveManager.restoreMetaInfo(SaveManager.java:832)
	at org.eclipse.core.internal.resources.SaveManager.restore(SaveManager.java:681)
	at org.eclipse.core.internal.resources.SaveManager.startup(SaveManager.java:1503)

...

INFO:  setpref 'targetPlatformPath=/build/hudson/jobs/xsl-easy Target Platform 3.5/builds/2010-09-06_10-27-06/archive//targetPlatform'
INFO:  import '/build/hudson/jobs/xslEasy40/workspace/de.softproject.xe.standalone.releng/build-3.6.cquery'
WARN:  Project de.softproject.xe.standalone.welcome references a closed project: de.softproject.xe.standalone
INFO:  Import complete.
INFO:  build
...



I do a clean of the workspace before populating again using a cquery. My buckminster commands look like this:

setpref targetPlatformPath="/build/hudson/jobs/xsl-easy Target Platform 3.5/builds/2010-09-06_10-27-06/archive//targetPlatform"
import  '/build/hudson/jobs/xslEasy40/workspace/de.softproject.xe.standalone.releng/build-3.6.cquery'
build
perform -P '/build/hudson/jobs/xslEasy40/workspace/de.softproject.xe.standalone.releng/buckminster_product.properties'  de.softproject.xe.standalone.releng#create.product.zip
perform de.softproject.xe.feature#site.p2


Has anyone seen this too? The problems show up BEFORE the first buckminster command is actually executed?
The build itself seems successful. It goes through and the build result works. Rolling Eyes It's just annoying.

best regards

-Thomas

Re: ERROR: Could not read metadata [message #558793 is a reply to message #558762] Tue, 14 September 2010 13:11 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes Utzig
Messages: 329
Registered: July 2009
Senior Member
Am 14.09.2010 13:15, schrieb Tomsen:
>
> I do a clean of the workspace before populating again using a cquery.

Hi Thomas,

when you say 'clean of the workspace', what exactly do you mean. It
sounds like Eclipse is starting up and the stuff in .metadata doesn't
match the actual workspace content.

Best regards,
Johannes
Re: ERROR: Could not read metadata [message #558806 is a reply to message #558793] Tue, 14 September 2010 14:04 Go to previous messageGo to next message
Tomsen  is currently offline Tomsen
Messages: 42
Registered: July 2010
Member
Johannes,
right on Smile

My "clean" only removed features/plugins and buckminster.output. I added a rm -R ${WORKSPACE}/.metadata and now it runs fine.

best regards

Thomas
Re: ERROR: Could not read metadata [message #1047001 is a reply to message #558806] Mon, 22 April 2013 16:56 Go to previous messageGo to next message
Gary Carnell is currently offline Gary Carnell
Messages: 1
Registered: April 2013
Junior Member
Hello,

Just had this one, removed the .lock file in .metadata and restarted Eclipse. Know idea why but this seems to be a "cure almost all" for startup problems I have got so far.

Regards, Gary
Re: ERROR: Could not read metadata [message #1047105 is a reply to message #1047001] Mon, 22 April 2013 19:50 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2013-04-22 19:24, Gary Carnell wrote:
> Hello,
>
> Just had this one, removed the .lock file in .metadata and restarted
> Eclipse. Know idea why but this seems to be a "cure almost all" for
> startup problems I have got so far.
>
> Regards, Gary

Did you send this to the right newsgroup?

- thomas
Previous Topic:p2 repository contains binaries which is not included.
Next Topic:eclipse.build does not generate class files when using Buckminster 4.2 on Jenkins
Goto Forum:
  


Current Time: Tue Oct 21 15:22:22 GMT 2014

Powered by FUDForum. Page generated in 0.01763 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software