Problem during meta-data refresh [message #1385374] |
Thu, 05 June 2014 19:51  |
Eclipse User |
|
|
|
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?
|
|
|
Re: Problem during meta-data refresh [message #1385390 is a reply to message #1385374] |
Fri, 06 June 2014 02:11   |
Eclipse User |
|
|
|
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
|
|
|
|
|
|
|
Re: Problem during meta-data refresh [message #1409392 is a reply to message #1408551] |
Sun, 17 August 2014 21:56  |
Eclipse User |
|
|
|
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...
|
|
|
Powered by
FUDForum. Page generated in 0.06273 seconds