|
|
|
Re: Feature Plugins not Materialized [message #663665 is a reply to message #663663] |
Wed, 06 April 2011 06:35 |
|
On 2011-04-06 08:20, Trip Gilman wrote:
> That's interesting. I would expect some errors like that, but they are not produced. The operation completes normally
> but only with some of the plugins resolved. I'll figure out where that bundle should come from to fix the rmap, but i'm
> still puzzled about the silent successful failure.
So am I. Exactly what command do you execute? Are you in the IDE or running headless? What log are you looking at?
- thomas
|
|
|
|
Re: Feature Plugins not Materialized [message #663674 is a reply to message #663667] |
Wed, 06 April 2011 07:18 |
|
On 2011-04-06 08:52, Trip Gilman wrote:
> I just looked in that location and what do you know there is an out of
> date version of my feature there.
That would explain a lot ;-)
> Now my question is where did this come
> from? It's a folder called features within my workspace root but isn't
> visible.
What you see in Eclipse and what you see in the file system might differ
a whole lot. Eclipse uses a virtual file system and the projects
physical location on disk may anywhere. It doesn't need to be below the
workspace root.
When Buckminster materializes into the workspace, the default behavior
is to create two folders, 'features' and 'plugins'. All workspace
features and plugins that Buckminster finds, will then end up beneath
those two folders. The layout is chosen to avoid collisions between
features and bundles with the same name. Again, please not that this is
just the physical location on disk. The projects will of course be bound
to the root of your Eclipse workspace.
- thomas
|
|
|
|
Powered by
FUDForum. Page generated in 0.03498 seconds