You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Richard S. Hall (JIRA)" <ji...@apache.org> on 2009/06/17 17:34:07 UTC

[jira] Closed: (FELIX-1247) BundleEvent.UNRESOLVED should be fired during update/uninstall not refresh

     [ https://issues.apache.org/jira/browse/FELIX-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Richard S. Hall closed FELIX-1247.
----------------------------------

    Resolution: Fixed

Committed a patch.

> BundleEvent.UNRESOLVED should be fired during update/uninstall not refresh
> --------------------------------------------------------------------------
>
>                 Key: FELIX-1247
>                 URL: https://issues.apache.org/jira/browse/FELIX-1247
>             Project: Felix
>          Issue Type: Bug
>          Components: Framework, Specification compliance
>    Affects Versions: felix-1.8.0
>            Reporter: Richard S. Hall
>            Assignee: Richard S. Hall
>             Fix For: felix-2.0.0
>
>
> After some discussion within CPEG it was clarified that BundleEvent.UNRESOLVED should be fired at the point of bundle update or uninstall. Previously Felix was firing it for update, but not for uninstall and was instead firing it during refresh. This new definition seems somewhat pointless since UNRESOLVED/UPDATED and UNRESOLVED/UNINSTALLED always happen in pairs now, but we are failing a TCK test as a result of our current implementation so we should change it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.