|
| Re: Resolve: Update plugins already present [message #653578 is a reply to message #653565] |
Thu, 10 February 2011 10:16   |
|
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 #653648 is a reply to message #653605] |
Thu, 10 February 2011 14:15 |
|
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
|
|
|
|
Powered by
FUDForum. Page generated in 0.02959 seconds
] 
Search
Help
Register
Login
Home
