Home » Archived » Buckminster » Getting subprojects into workspace (Do I need to use generators?)
|
| Re: Getting subprojects into workspace (Do I need to use generators?) [message #500242 is a reply to message #500067] |
Wed, 25 November 2009 13:28   |
 Henrik Lindberg
Messages: 2509
Registered: July 2009 |
Senior Member |
|
|
Hi,
Since the four parts are projects, and separately adressable (have a
name, a version, and can be accessed) you do not have to use generators
(which are typically used when the named thing does not exist anywhere
until some other component have performed an action). The question here
is if your components B-E are free-standing or if you need all of them
if you need one.
The first step is to make sure that your RMAP contains rules that makes
it possible to find all your components A-E. Try it by editing your
RMAP, and then validate by running a CQUERY for each of the components.
If your components are free standing, then you should be able to state
dependencies on them, and have the transitive closure materialized.
If they are not freestanding, then generators could be used. You then
need to include the component A in your configuration (i.e. depend on
it). The component A would then need to contain declarations that it
generates the other components.
First question: are your components B-E independent/free-standing?
- henrik
On 11/24/09 9:11 PM, Corey Zimmet wrote:
> I have a legacy project that was broken up into 4 sub-projects. Normally, I
> check out the project outside of eclipse and import the 4 subprojects into
> my workspace. I then import the rest of my components. All are osgi bundles.
>
> I have been trying to replicate this action via a cquery/mspec in
> Buckminster with no success. I can use an mspec to bring the main project
> down to the filesystem. However, I am having trouble when other components
> that depend on the 4 subcomponents try to resolve dependencies.
>
> For example
>
> /A/.project
> /A/B/.project
> /A/C/.project
> /A/D/.project
> /A/E/.project
>
> /F which depends on B,C,D,E
>
> Is this a situation where a "generator via cspecx" in Project A would be
> used? How do I get A to advertize that it offers B,C,D and E?
>
> Thanks,
> Corey
>
>
>
|
|
|
| Re: Getting subprojects into workspace (Do I need to use generators?) [message #500291 is a reply to message #500242] |
Wed, 25 November 2009 15:28 |
Corey Zimmet
Messages: 7
Registered: July 2009 |
Junior Member |
|
|
The components are free standing. However component A needs to be
excluded from the workspace (which is why I have been using a file
system materializer in an MSPEC). Component A is an artifact from an
earlier RCP that needs to be present above B-E for legacy purposes.
However, component A's presence in the workspace is not desired. If
there was a way for Component A to let the resolution process know that
it needs to wait until Componet A is brought down to look for B,C,D, and
E and then look at the file system, that would work.
Even though, I am not generating anything. I thought that using a
generator would get me the deferred resolution for which I am looking.
Thanks,
Corey
Henrik Lindberg wrote:
> Hi,
> Since the four parts are projects, and separately adressable (have a
> name, a version, and can be accessed) you do not have to use generators
> (which are typically used when the named thing does not exist anywhere
> until some other component have performed an action). The question here
> is if your components B-E are free-standing or if you need all of them
> if you need one.
>
> The first step is to make sure that your RMAP contains rules that makes
> it possible to find all your components A-E. Try it by editing your
> RMAP, and then validate by running a CQUERY for each of the components.
>
> If your components are free standing, then you should be able to state
> dependencies on them, and have the transitive closure materialized.
>
> If they are not freestanding, then generators could be used. You then
> need to include the component A in your configuration (i.e. depend on
> it). The component A would then need to contain declarations that it
> generates the other components.
>
> First question: are your components B-E independent/free-standing?
>
> - henrik
>
> On 11/24/09 9:11 PM, Corey Zimmet wrote:
>> I have a legacy project that was broken up into 4 sub-projects.
>> Normally, I
>> check out the project outside of eclipse and import the 4 subprojects
>> into
>> my workspace. I then import the rest of my components. All are osgi
>> bundles.
>>
>> I have been trying to replicate this action via a cquery/mspec in
>> Buckminster with no success. I can use an mspec to bring the main
>> project
>> down to the filesystem. However, I am having trouble when other
>> components
>> that depend on the 4 subcomponents try to resolve dependencies.
>>
>> For example
>>
>> /A/.project
>> /A/B/.project
>> /A/C/.project
>> /A/D/.project
>> /A/E/.project
>>
>> /F which depends on B,C,D,E
>>
>> Is this a situation where a "generator via cspecx" in Project A would be
>> used? How do I get A to advertize that it offers B,C,D and E?
>>
>> Thanks,
>> Corey
>>
>>
>>
>
|
|
|
Goto Forum:
Current Time: Thu Jan 16 23:19:57 GMT 2025
Powered by FUDForum. Page generated in 0.02871 seconds |
] 
Search
Help
Register
Login
Home
