felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Süß (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FELIX-4459) Enforcing parallel Installation of Bundles with same symbolic name
Date Fri, 14 Mar 2014 11:57:46 GMT

    [ https://issues.apache.org/jira/browse/FELIX-4459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934913#comment-13934913

Dominik Süß commented on FELIX-4459:

[~cziegeler] what about installations not performed directly via webconsole - and how to identify
which one to update if two with same symbolic name are availble (potentially the newer one
but a new one could also replace both).

> Enforcing parallel Installation of Bundles with same symbolic name
> ------------------------------------------------------------------
>                 Key: FELIX-4459
>                 URL: https://issues.apache.org/jira/browse/FELIX-4459
>             Project: Felix
>          Issue Type: Improvement
>          Components: Web Console
>            Reporter: Dominik Süß
> Currently it seems not to be possible to install two bundles with the same symbolic name
but differnt version to Felix (it is always assumed to be an update. 
> In cases like commons-lang and commons-lang3 (symbolic name org.apache.commons.lang)
this creates a problem since the exported APIs are different and you might need to use both
(dependencies of third bundles).
> This currently leads to the awkward situation that one of both needs to be wrapped in
a custom bundle to have both APIs present in the same instance. 
> It should be possible to enforce installation of parallel bundles with differnt version
via webconsole. (only question I cannot anwer right now is how update would detect which one
to update for a further version).

This message was sent by Atlassian JIRA

View raw message