Eclipse Community Forums: Buckminster » Resolve: Update plugins already present

Home » Archived » Buckminster » Resolve: Update plugins already present

Resolve: Update plugins already present [message #653565]

Thu, 10 February 2011 04:24

Eclipse User

Hi there,

I used a component query to resolve a target platform which I then set
as active target platform in my IDE. The query references a few bundles
from p2 repositories.

Let's say buckminster used bundle A in version 1.0.0 from a p2 repo. Now
someone created A 1.1.0 and published the new version to the same p2
repo. If I run the query again, buckminster does not do anything because
A is already present in the target platform. Is there a way to tell him
to update bundles if there is a newer version available? Or can I only
make this work if some other bundle explicitly requires A >=1.1.0?

Regards,
Daniel

Re: Resolve: Update plugins already present [message #653578 is a reply to message #653565]

Thu, 10 February 2011 05:16

Eclipse User

On 2011-02-10 10:24, Daniel Weber wrote:
> Hi there,
>
> I used a component query to resolve a target platform which I then set as active target platform in my IDE. The query
> references a few bundles from p2 repositories.
>
> Let's say buckminster used bundle A in version 1.0.0 from a p2 repo. Now someone created A 1.1.0 and published the new
> version to the same p2 repo. If I run the query again, buckminster does not do anything because A is already present in
> the target platform. Is there a way to tell him to update bundles if there is a newer version available? Or can I only
> make this work if some other bundle explicitly requires A >=1.1.0?
>
Add an advisor node in your CQUERY that matches everything (use pattern ".*"). Click on Resolution Scope and uncheck
"Target Platform". That will force Buckminster to consult the RMAP even if satisfying bundles exists in the TP.

In XML, the added element looks like this:

<cq:advisorNode namePattern=".*" useMaterialization="false" useTargetPlatform="false"/>

If you have more advisor nodes then you must add this one last and uncheck "Target Platform" in all of them.

- thomas

Re: Resolve: Update plugins already present [message #653605 is a reply to message #653578]

Thu, 10 February 2011 06:38

Eclipse User

Hi Thomas,

thanks for your quick reply :)

On 10.02.2011 11:16, Thomas Hallgren wrote:
> Add an advisor node in your CQUERY that matches everything (use pattern
> ".*"). Click on Resolution Scope and uncheck "Target Platform". That
> will force Buckminster to consult the RMAP even if satisfying bundles
> exists in the TP.

This does the trick, great! So when resolving dependencies buckminster
now ignores dependencies, but when actually materializing them it will
not re-download and install components which are up-to-date, correct?

Thanks,
Daniel

Re: Resolve: Update plugins already present [message #653648 is a reply to message #653605]

Thu, 10 February 2011 09:15

Eclipse User

On 2011-02-10 12:38, Daniel Weber wrote:
> This does the trick, great! So when resolving dependencies buckminster now ignores dependencies, but when actually
> materializing them it will not re-download and install components which are up-to-date, correct?
>
No, Buckminster doesn't ignore dependencies. It just ignores the target platform while resolving them.

- thomas

Re: Resolve: Update plugins already present [message #653664 is a reply to message #653648]

Thu, 10 February 2011 10:36

Eclipse User

On 10.02.2011 15:15, Thomas Hallgren wrote:
> No, Buckminster doesn't ignore dependencies. It just ignores the target
> platform while resolving them.

That's not what I wrote but what I meant ;)

Thanks a lot,
Daniel

Previous Topic:	Dependency resolution - too broad?
Next Topic:	buckmminster and custom build callback

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 07:20:34 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter