Eclipse Community Forums: Buckminster » Problem during meta-data refresh

Help

Home

Home » Archived » Buckminster » Problem during meta-data refresh

Show: Today's Messages :: Show Polls :: Message Navigator

Problem during meta-data refresh [message #1385374]

Thu, 05 June 2014 23:51

Al B

Messages: 130
Registered: July 2009

Senior Member

With Juno, we are able to create build artifacts, but we try with Kepler 4.3, then we get this exception:

Problem during meta-data refresh: No component named _feature_gov.nasa.arc.spife is known to Buckminster
org.eclipse.buckminster.core.metadata.MissingComponentException: No component named _feature_gov.nasa.arc.spife is known to Buckminster
at org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:179)
at org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:185)
at org.eclipse.buckminster.core.metadata.MetadataSynchronizer.refreshProject(MetadataSynchronizer.java:295)
at org.eclipse.buckminster.core.metadata.MetadataSynchronizer.workspaceCatchUp(MetadataSynchronizer.java:394)
at org.eclipse.buckminster.core.metadata.MetadataSynchronizer$WorkspaceCatchUpJob.run(MetadataSynchronizer.java:185)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)

Has anyone experienced this issue with Kepler?

Report message to a moderator

Re: Problem during meta-data refresh [message #1385390 is a reply to message #1385374]

Fri, 06 June 2014 06:11

Lorenzo Bettini

Messages: 1812
Registered: July 2009
Location: Firenze, Italy

Senior Member

On 06/06/2014 01:51, Al B wrote:
> With Juno, we are able to create build artifacts, but we try with Kepler
> 4.3, then we get this exception:
>
> Problem during meta-data refresh: No component named
> _feature_gov.nasa.arc.spife is known to Buckminster
> org.eclipse.buckminster.core.metadata.MissingComponentException: No
> component named _feature_gov.nasa.arc.spife is known to Buckminster
> at
> org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:179)
>
> at
> org.eclipse.buckminster.core.resolver.LocalResolver.fromPath(LocalResolver.java:185)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer.refreshProject(MetadataSynchronizer.java:295)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer.workspaceCatchUp(MetadataSynchronizer.java:394)
>
> at
> org.eclipse.buckminster.core.metadata.MetadataSynchronizer$WorkspaceCatchUpJob.run(MetadataSynchronizer.java:185)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
>
> Has anyone experienced this issue with Kepler?

OK, I see you opened another thread, so I'll answer here as well :)

do you get this error in the IDE or during the headless build? Are you
using Buckminster for Kepler?

cheers
Lorenzo

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition

Report message to a moderator

Re: Problem during meta-data refresh [message #1385400 is a reply to message #1385390]

Fri, 06 June 2014 08:15

Al B

Messages: 130
Registered: July 2009

Senior Member

I get this error in the workbench, using Buckminster for Kepler.

http://download.eclipse.org/tools/buckminster/updates-4.3

Report message to a moderator

Re: Problem during meta-data refresh [message #1385511 is a reply to message #1385400]

Sun, 08 June 2014 07:21

Lorenzo Bettini

Messages: 1812
Registered: July 2009
Location: Firenze, Italy

Senior Member

On 06/06/2014 10:15, Al B wrote:
> I get this error in the workbench, using Buckminster for Kepler.
>
> http://download.eclipse.org/tools/buckminster/updates-4.3

You may want to try with a fresh workspace... I don't know otherwise.

--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book

Report message to a moderator

Re: Problem during meta-data refresh [message #1408497 is a reply to message #1385511]

Fri, 15 August 2014 07:50

Knut Wannheden

Messages: 298
Registered: July 2009

Senior Member

I just had a problem like this as well. It turned out that the feature Buckminster claimed not knowing had an included feature duplicated in the feature.xml. I.e. there were two <include> elements for the same feature. While PDE doesn't seem to care much about this, it doesn't make much sense. But in this case the Buckminster logging is also not very helpful.

Report message to a moderator

Re: Problem during meta-data refresh [message #1408551 is a reply to message #1408497]

Fri, 15 August 2014 11:08

Al B

Messages: 47
Registered: June 2012

Member

Wow, thanks Knut! You are right. I had two "org.eclipse.emf.common" declared as includes. I still cannot create a build, but I'm now getting a more meaningful error. Thanks again.

Report message to a moderator

Re: Problem during meta-data refresh [message #1409392 is a reply to message #1408551]

Mon, 18 August 2014 01:56

Knut Wannheden

Messages: 298
Registered: July 2009

Senior Member

Glad that helped in your case!

I still have cases where I run into the same "No component named <foo> is known to Buckminster" problem and don't know what the issue is. The plug-ins in question are clearly part of the target platform, but there is no logging from Buckminster which would help me pin this down. If I get time I will try to debug it...

Report message to a moderator

Previous Topic:	Circular component dependency JDT -> OTDT -> JDT
Next Topic:	SVN Repo - head instead of trunk

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 21:51:28 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter