Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » How to debug: "No component XXX is known to Buckminster"?
How to debug: "No component XXX is known to Buckminster"? [message #630290] Fri, 01 October 2010 08:33 Go to next message
Daniel Ford is currently offline Daniel Ford
Messages: 138
Registered: July 2009
Location: New York
Senior Member
I'm using Hudson and Buckminster to try to automate the build of an RCP.
I'm working through the usual newbie problems, but have hit a wall on
one and hope I can get some advice on how to debug it.

I've got most things working, creating the target platform, checking out
and building the workspace, etc., but when I try to "perform" an action
(site.p2) on a component, I get an error message stating that the
component is not known to Buckminster.

"No component XXX is known to Buckminster"

If I look in the workspace created during the build, my component is
there, and I can trigger the action on it in another workspace without
any problems using Eclipse.

It is as if Buckminster was using a different workspace, one without the
component, except it is able to find the properties file in the same
workspace (different component) I provide on the command line.

I've played around with enabling the DEBUG level on the logging hoping
to get more information (I didn't), and I've even changed the component
name to see if a different component could be found (it wasn't).

Any hints on what to try next?

Dan
Re: How to debug: "No component XXX is known to Buckminster"? [message #630304 is a reply to message #630290] Fri, 01 October 2010 09:28 Go to previous messageGo to next message
Daniel Ford is currently offline Daniel Ford
Messages: 138
Registered: July 2009
Location: New York
Senior Member
I seemed to have fixed this one, but I'm a bit confused. Poking around
a bit I realized that the component that I was building (a feature
describing an update site) was not the target of my workspace import
cquery, instead, I was using one component below it in the dependency
tree. The confusing part is that the top-level component was still
being imported into the workspace from my repository (how did that
happen?). So, once I changed the cquery to resolve the top-level
component, it was found, and things started working.

Dan


On 10/1/2010 8:33 AM, Daniel Ford wrote:
> I'm using Hudson and Buckminster to try to automate the build of an RCP.
> I'm working through the usual newbie problems, but have hit a wall on
> one and hope I can get some advice on how to debug it.
>
> I've got most things working, creating the target platform, checking out
> and building the workspace, etc., but when I try to "perform" an action
> (site.p2) on a component, I get an error message stating that the
> component is not known to Buckminster.
>
> "No component XXX is known to Buckminster"
>
> If I look in the workspace created during the build, my component is
> there, and I can trigger the action on it in another workspace without
> any problems using Eclipse.
>
> It is as if Buckminster was using a different workspace, one without the
> component, except it is able to find the properties file in the same
> workspace (different component) I provide on the command line.
>
> I've played around with enabling the DEBUG level on the logging hoping
> to get more information (I didn't), and I've even changed the component
> name to see if a different component could be found (it wasn't).
>
> Any hints on what to try next?
>
> Dan
Re: How to debug: "No component XXX is known to Buckminster"? [message #630367 is a reply to message #630304] Fri, 01 October 2010 14:23 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3208
Registered: July 2009
Senior Member
On 2010-10-01 15:28, Daniel Ford wrote:
> ... The confusing part is that the top-level component was still being
> imported into the workspace from my repository (how did that happen?).

No idea. Buckminster has no psychic abilities so it didn't guess what
you really intended (although I think it would have been a really cool
feature ;-) ).

- thomas
Re: How to debug: "No component XXX is known to Buckminster"? [message #630616 is a reply to message #630304] Mon, 04 October 2010 07:56 Go to previous message
Johannes Utzig is currently offline Johannes Utzig
Messages: 329
Registered: July 2009
Senior Member
Hi Daniel,

Am 01.10.2010 15:28, schrieb Daniel Ford:
> I seemed to have fixed this one, but I'm a bit confused. Poking around
> a bit I realized that the component that I was building (a feature
> describing an update site) was not the target of my workspace import
> cquery, instead, I was using one component below it in the dependency
> tree. The confusing part is that the top-level component was still being
> imported into the workspace from my repository (how did that happen?).
> So, once I changed the cquery to resolve the top-level component, it was
> found, and things started working.
>
> Dan
>
>

My guess is that Hudson does the checkout for you and you use a local
resolver for Buckminster? In that case Hudson probably checks out your
top-level component into the job workspace which by default equals the
buckminster workspace.
But since you didn't explicitly query the top level component
Buckminster never tried to resolve it and therefore never created an
eclipse project.
So even if the top level component was pysically present in the right
location, there was no eclipse project for it and that's why it was
invisible for buckminster.

Best regards
Johannes
Previous Topic:Buckminster cvs materializing, uses a proxy, how is this configured?
Next Topic:P2 located in SVN
Goto Forum:
  


Current Time: Wed Apr 16 00:46:47 EDT 2014

Powered by FUDForum. Page generated in 0.01601 seconds