| Problem with plugin-based products [message #1096404] |
Wed, 28 August 2013 10:48  |
|
Hi,
Can someone make a sense out of this error?
Project refresh on org.eclipse.emf.cdo.server.product.tcp_h2-feature failed: No component named
org.eclipse.emf.cdo.server.product.tcp_h2-feature is known to Buckminster
org.eclipse.buckminster.core.metadata.MissingComponentException: No component named
org.eclipse.emf.cdo.server.product.tcp_h2-feature 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$MetadataRefreshJob.run(MetadataSynchronizer.java:126)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
The error message "No component named org.eclipse.emf.cdo.server.product.tcp_h2-feature is known to Buckminster" is
strange because that is indeed not a component ID but rather a project name (not identical). Is that a bug in Buckminster?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: Problem with plugin-based products [message #1100671 is a reply to message #1096404] |
Tue, 03 September 2013 12:25  |
|
Hi
do you get this problem in the workbench or headlessly?
In the workbench I usually get these problems when I refactor (rename) a
project...
cheers
Lorenzo
On 08/28/2013 12:48 PM, Eike Stepper wrote:
> Hi,
>
> Can someone make a sense out of this error?
>
> Project refresh on org.eclipse.emf.cdo.server.product.tcp_h2-feature
> failed: No component named
> org.eclipse.emf.cdo.server.product.tcp_h2-feature is known to Buckminster
> org.eclipse.buckminster.core.metadata.MissingComponentException: No
> component named org.eclipse.emf.cdo.server.product.tcp_h2-feature 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$MetadataRefreshJob.run(MetadataSynchronizer.java:126)
>
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
>
> The error message "No component named
> org.eclipse.emf.cdo.server.product.tcp_h2-feature is known to
> Buckminster" is strange because that is indeed not a component ID but
> rather a project name (not identical). Is that a bug in Buckminster?
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
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
|
|
|
| Re: Problem with plugin-based products [message #1100711 is a reply to message #1100671] |
Tue, 03 September 2013 13:32 |
|
Am 03.09.2013 14:25, schrieb Lorenzo Bettini:
> Hi
>
> do you get this problem in the workbench or headlessly?
Hmm, can't remember now that a week has passed ;-(
> In the workbench I usually get these problems when I refactor (rename) a
> project...
The same problem? With "-feature" appended to a *product name* ?
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
> cheers
> Lorenzo
>
> On 08/28/2013 12:48 PM, Eike Stepper wrote:
>> Hi,
>>
>> Can someone make a sense out of this error?
>>
>> Project refresh on org.eclipse.emf.cdo.server.product.tcp_h2-feature
>> failed: No component named
>> org.eclipse.emf.cdo.server.product.tcp_h2-feature is known to Buckminster
>> org.eclipse.buckminster.core.metadata.MissingComponentException: No
>> component named org.eclipse.emf.cdo.server.product.tcp_h2-feature 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$MetadataRefreshJob.run(MetadataSynchronizer.java:126)
>>
>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
>>
>> The error message "No component named
>> org.eclipse.emf.cdo.server.product.tcp_h2-feature is known to
>> Buckminster" is strange because that is indeed not a component ID but
>> rather a project name (not identical). Is that a bug in Buckminster?
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: Problem with plugin-based products [message #1100728 is a reply to message #1100711] |
Tue, 03 September 2013 14:04 |
|
On 09/03/2013 03:32 PM, Eike Stepper wrote:
> Am 03.09.2013 14:25, schrieb Lorenzo Bettini:
>> Hi
>>
>> do you get this problem in the workbench or headlessly?
> Hmm, can't remember now that a week has passed ;-(
>
>> In the workbench I usually get these problems when I refactor (rename) a
>> project...
> The same problem? With "-feature" appended to a *product name* ?
No, in my case such problems happen if I rename a project or if I move
the project to a different location (with "Refactor"). When this
happens, in the workbench, I have to delete the project from the
workspace, restart Eclipse, and the reimport the project...
--
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.01617 seconds
] 
Search
Help
Register
Login
Home
