| Materialized directory structure [message #385210] |
Tue, 12 May 2009 15:05  |
Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
When I perform the demo cquery for org.demo.hello.xml.world, in my
workspace I end up with the three projects in a directory structure of:
workspace/org.demo.worlds/
workspace/plugins/org.demo.hello.xml.world
workspace/plugins/org.demo.xml.provider
Is this the default layout for cqueries?
We have traditionally used a flat workspace layout for our projects.
What is the simplest way to materialize to a flattened workspace
(removing the plugins directory and the features directories for more
complex projects)?
Can it be done by the user through the Buckminster Component Query
Wizard or does one have to write a MSpec to do this?
- John
|
|
|
| Re: Materialized directory structure [message #385386 is a reply to message #385210] |
Mon, 18 May 2009 20:54  |
| Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Answering my own question here. (Please correct if I am wrong.)
John E. Conlon wrote:
> When I perform the demo cquery for org.demo.hello.xml.world, in my
> workspace I end up with the three projects in a directory structure of:
>
> workspace/org.demo.worlds/
> workspace/plugins/org.demo.hello.xml.world
> workspace/plugins/org.demo.xml.provider
>
>
> Is this the default layout for cqueries?
Appears to be so. For reasons guessed at below.
>
> We have traditionally used a flat workspace layout for our projects.
>
> What is the simplest way to materialize to a flattened workspace
> (removing the plugins directory and the features directories for more
> complex projects)?
Not sure of the answer to this in the case of projects with multiple
components. Using the Query wizard to direct the materialization is a
hassle if there are too many components to materialize.
Will investigate the MSpec approach.
>
> Can it be done by the user through the Buckminster Component Query
> Wizard or does one have to write a MSpec to do this?
Yes this can be done in the Buckminster Component Query Wizard, by
unchecking 'use defaults' and pressing the advanced button.
Destination: Workspace
Parent Folder: <Root directory of your workspace>
Workspace: <Root directory of your workspace>
Project name: <Name of your project if it is different from the name of
the compnent id>
It is the last point that I 'guess' is the reason for the
plugins/features subdirectory: A feature and a plugin often use the
same component name. The subdirectories keep them separate.
>
>
> - John
>
>
>
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.06000 seconds
] 
Search
Help
Register
Login
Home
