[
https://issues.apache.org/jira/browse/FELIX-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-701:
------------------------------------
Attachment: FELIX-701.patch
Proposed fix, which stops the bundle to be updated before the update and
starting the bundle again, if everything is done.
Possibly the ResolverImpl.deploy should be modified to not abort on any
exception from bundle update or installation ?
> Installation failure when updating bundles with required bundles
> ----------------------------------------------------------------
>
> Key: FELIX-701
> URL: https://issues.apache.org/jira/browse/FELIX-701
> Project: Felix
> Issue Type: Bug
> Components: Bundle Repository (OBR)
> Reporter: Felix Meschberger
> Attachments: FELIX-701.patch
>
>
> Consider a system with two bundles installed:
> Bundle A, Version 1, imports package B.x with version 1, started
> Bundle B, Version 1, exports package B.x with version 1, started
> Now, Bundle A should be updated to version 2:
> Bundle A, Version 2, imports package B.x with version 2
> This causes OBR to select version 2 of Bundle B to satisfy the requirement of
> version 2 of Bundle A.
> Bundle B, Version 2, exports package B.x with version 2
> Now, the ResolverImpl will try to update Bundle A with the new version, which
> fails because Bundle A is automatically started again by the framework but
> does not resolve due to the version mismatch on the package import. This
> throws an exception causing the ResolverImpl to abort the deployment.
> A simple fix to this problem is, that the ResolverImpl temporarily stops
> Bundle A before updating it and starting Bundle A again after the update.
> This allows the resolver to continue with the deployment of the required
> bundle and finally starting everything again.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
