|
|
|
Re: Updating workspace [message #554985 is a reply to message #554955] |
Wed, 25 August 2010 05:50 |
|
On 08/24/2010 11:36 PM, Alex wrote:
> ... This is what I did:
>
> <cq:advisorNode namePattern="^com\.iwaysoftware(\..+)?"
> useMaterialization="false" useWorkspace="false"/>
>
Only the first advisor node that matches is used. Do you have some other node that is placed before this one that match
the same components?
- thomas
|
|
|
|
Re: Updating workspace [message #555151 is a reply to message #555077] |
Wed, 25 August 2010 15:45 |
|
On 08/25/2010 01:53 PM, Alex wrote:
> There is no other node before this one except root. Also, advisor will
> match across different types as well, or do I have to specify the type?
>
No. If no type is specified, all types are matched.
- thomas
|
|
|
Re: Updating workspace [message #555160 is a reply to message #555151] |
Wed, 25 August 2010 16:10 |
Alex Kravets Messages: 561 Registered: November 2009 |
Senior Member |
|
|
Thanks Thomas,
I did notice something else, one of the features contains cspec - it's an update site feature, and this gets updated every time. I also have this feature listed as dependency in the cspex of the build project so that buckminster materializes it during cquery import. Now, I tried doing same for another feature that does not get updated (create cspec in the feature, add it as dependency in cspex), but this does not work. Besides, even if it did, it would mean I need to add all dependencies in the cspex?
I also remember that Henrik mentioned that buckminster 3.5 needs mspec to perform materialization, but I am not sure if I needed it in my case.
thanks,
Alex
|
|
|
|
Re: Updating workspace [message #555176 is a reply to message #555160] |
Wed, 25 August 2010 16:52 |
Henrik Lindberg Messages: 2509 Registered: July 2009 |
Senior Member |
|
|
A cspex is a decoration on the automatically generated cspec - so there
is no need to restate what has already been discovered and translated by
buckminster.
If a component is treated as a native buckminster component, it can have
just a cspec (since there is no discovery, and hence nothing to decorate).
An mspec is needed in 3.5 if materialization should go to different places.
Regards
- henrik
On 8/25/10 6:10 PM, Alex wrote:
> Thanks Thomas,
>
> I did notice something else, one of the features contains cspec - it's
> an update site feature, and this gets updated every time. I also have
> this feature listed as dependency in the cspex of the build project so
> that buckminster materializes it during cquery import. Now, I tried
> doing same for another feature that does not get updated (create cspec
> in the feature, add it as dependency in cspex), but this does not work.
> Besides, even if it did, it would mean I need to add all dependencies in
> the cspex?
> I also remember that Henrik mentioned that buckminster 3.5 needs mspec
> to perform materialization, but I am not sure if I needed it in my case.
>
> thanks,
> Alex
>
>
|
|
|
|
Re: Updating workspace [message #555209 is a reply to message #555173] |
Wed, 25 August 2010 20:25 |
|
On 08/25/2010 07:11 PM, Alex wrote:
> Something else I noticed. If I use buckminster 3.5, then update site
> project updates fine, however if I use buckminster 3.6 it does not.
If that's the case, then it's a regression that deserves a bugzilla.
- thomas
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04213 seconds