You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2012/10/02 17:55:08 UTC

[jira] [Commented] (SLING-2570) Use Wiring API to check whether Installer Core bundle is affect by a bundle update

    [ https://issues.apache.org/jira/browse/SLING-2570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467812#comment-13467812 ] 

Carsten Ziegeler commented on SLING-2570:
-----------------------------------------

This is more tricky than I thought:
- we need framework 4.3 to have the wiring package
- unfortunately if compiled against 4.3, the code doesn't work in 4.2 anymore
- this is not just because of the import package (which is fine and solved by hard coding)
- e.g. Version.compareTo changed from compareTo(Object) to compareTo(Version) which doesn't work on 4.2 as this method doesn't exist

I'm quiet unsure how to proceed and solve this
                
> Use Wiring API to check whether Installer Core bundle is affect by a bundle update
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-2570
>                 URL: https://issues.apache.org/jira/browse/SLING-2570
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>    Affects Versions: Installer Core 3.3.8
>            Reporter: Felix Meschberger
>            Assignee: Carsten Ziegeler
>             Fix For: Installer Core 3.4.0
>
>         Attachments: SLING-2570.patch
>
>
> Recently support has been built into the OSGi installer to check whether update of bundles affects the Installer bundle itself (for wiring reasons). This is currently implemented using the deprecated PackageAdmin service.
> For newer platforms where the OSGi Wiring API is available, the newer API should be used for that check. This makes our code simpler and cleaner.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira