On 7/25/12 09:18 , Dan Gravell wrote:
If you refresh A after updating it, then both B and C should be refreshed
too since they depend on it. Then everyone will point to the same version
of 'a'. No?
Errr... I'm embarrassed to say I don't know.
I'm using OBR and deploying a bunch of bundles (of which A, B and C are a
subset) from a repository.xml. Basically I use a filter string to specify
all of my bundles and then say deploy(START). _Then_ I do the refresh, but
the uses constraints violation has already happened by then (when I did the
deploy). Is there a better way? Should I take each resource and deploy,
refresh, deploy, refresh? I thought refresh was supposed to be grouped to
some extent?
Yeah, OBR doesn't do this automatically and it should, see:
https://issues.apache.org/jira/browse/FELIX-3566
I'll probably go ahead and apply the above patch to OBR, but I'm not
sure when it will actually be released. In the meantime, you can simply
refresh without specifying any bundles after performing an OBR deploy.
Refreshing without specifying any target bundles will only refresh
bundles that were updated or uninstalled.
If you need to do multiple deploy operations, then yeah it is better to
do the refresh at the end.
-> richard
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
