Eclipse Community Forums: Buckminster

Home » Archived » Buckminster » Updating workspace

Tue, 24 August 2010 17:36

Eclipse User

Hi,

When I run the build components that are already in the workspace are not being updated. I found a post that discusses tthis issue http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg0071 1.html, and added advisor node to cquery, but still components are not being updated. This is what I did:

<cq:advisorNode namePattern="^com\.iwaysoftware(\..+)?" useMaterialization="false" useWorkspace="false"/>

What can I check to see why update is not being executed?

thanks,
Alex

[Updated on: Tue, 24 August 2010 17:38] by Moderator

Re: Updating workspace [message #554970 is a reply to message #554955]

Tue, 24 August 2010 20:57

Eclipse User

Materialization is only performed when a query is executed. Are you
rerunning the query?

- henrik

On 8/24/10 11:36 PM, Alex wrote:
> Hi,
>
> When I run the build components that are already in the workspace are
> not being updated. I found a post that discusses tthis issue
> http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg0071 1.html, and
> added advisor node to cquery, but still components are not being
> updated. This is what I did:
>
> <cq:advisorNode namePattern="^com\.iwaysoftware(\..+)?"
> useMaterialization="false" useWorkspace="false"/>
>
>
> thanks,
> Alex
>
>
>

Re: Updating workspace [message #554971 is a reply to message #554970]

Tue, 24 August 2010 22:03

Eclipse User

Yes, locally in cquery I execute resolve and materialize but no incoming changes in bundles are updated.

I do see this in the log

com.iwaysoftware.logging:osgi.bundle: Rejecting provider local(materialized): Materializations disabled in query
com.iwaysoftware.logging:osgi.bundle: Rejecting provider local(workspace): Workspace disabled in query
com.iwaysoftware.logging:osgi.bundle: Trying provider local(target)
com.iwaysoftware.logging:osgi.bundle: Found match 0.1.0.qualifier
com.iwaysoftware.logging:osgi.bundle: Found match com.iwaysoftware.logging:osgi.bundle$0.1.0.qualifier

How can my plugins be found in target platform? Also, if I only leave Resolution Service to be searched, I see that match is found remotely via rmap, but then I get exceptions because dependencies that are in eclipse repositories are not found.

thanks,
Alex

Re: Updating workspace [message #554985 is a reply to message #554955]

Wed, 25 August 2010 01:50

Eclipse User

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 #555077 is a reply to message #554985]

Wed, 25 August 2010 07:53

Eclipse User

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?

thanks,
Alex

Re: Updating workspace [message #555151 is a reply to message #555077]

Wed, 25 August 2010 11:45

Eclipse User

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 12:10

Eclipse User

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 #555173 is a reply to message #555160]

Wed, 25 August 2010 13:11

Eclipse User

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.

Re: Updating workspace [message #555176 is a reply to message #555160]

Wed, 25 August 2010 12:52

Eclipse User

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 #555177 is a reply to message #555176]

Wed, 25 August 2010 13:22

Eclipse User

Thanks Henrik,

Quote:

An mspec is needed in 3.5 if materialization should go to different places.

Then this has no affect during update as components are already where they need to be. I don't understand why local provider is chosen during materialization when advisor excludes it.

Alex

Re: Updating workspace [message #555209 is a reply to message #555173]

Wed, 25 August 2010 16:25

Eclipse User

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

Re: Updating workspace [message #555211 is a reply to message #555209]

Wed, 25 August 2010 16:45

Eclipse User

Should bugzilla only include 3.5 to 3.6 regression, or do you think there might be something wrong with updating of materialized components as well?

Re: Updating workspace [message #555216 is a reply to message #555211]

Wed, 25 August 2010 17:35

Eclipse User

Alex wrote on Wed, 25 August 2010 16:45

Should bugzilla only include 3.5 to 3.6 regression, or do you think there might be something wrong with updating of materialized components as well?

What I meant was the update happens only for component of type buckminster in 3.5, so should I open bugzilla as that or open it to updating in general - for all component types?

thanks,
Alex

Re: Updating workspace [message #555345 is a reply to message #555216]

Thu, 26 August 2010 07:41

Eclipse User

Just describe what you were able to figure out.
- henrik
On 8/25/10 11:35 PM, Alex wrote:
> Alex wrote on Wed, 25 August 2010 16:45
>> Should bugzilla only include 3.5 to 3.6 regression, or do you think
>> there might be something wrong with updating of materialized
>> components as well?
>
> What I meant was the update happens only for component of type
> buckminster in 3.5, so should I open bugzilla as that or open it to
> updating in general - for all component types?
>
> thanks,
> Alex

Previous Topic:	Compile JET templates during a Buckminster PDE Build
Next Topic:	Build for TP 3.5 contains 3.6 plugins

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 12 12:32:45 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter