You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@aries.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2013/11/05 23:16:18 UTC

[jira] [Issue Comment Deleted] (ARIES-1131) Extend blueprint.service import version range in blueprint.webosgi bundle

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

Sergey Beryozkin updated ARIES-1131:
------------------------------------

    Comment: was deleted

(was: Hi JB, thanks for the initial fix, would like to confirm that the 'http' feature does not provide a support for a "webbundle:" protocol which blueprint-web-osgi would support, so I believe we need a 'war' dependency which does offer a support for it.

Cheers, Sergey )

> Extend blueprint.service import version range in blueprint.webosgi bundle
> -------------------------------------------------------------------------
>
>                 Key: ARIES-1131
>                 URL: https://issues.apache.org/jira/browse/ARIES-1131
>             Project: Aries
>          Issue Type: Bug
>          Components: Web
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Sergey Beryozkin
>         Attachments: ARIES-1131.patch
>
>
> blueprint.webosgi 1.0.0 bundle imports org.apache.aries.blueprint.service package with version 1.3.0.
> Unfortunately, blueprint-core 1.3.0 exports this package with version 1.2.0 (which is not correct, I will create another Jira for that).
> In order to be able to use blueprint.webosgi with blueprint-core 1.3.0, the import version range should be extended to [1.2, 2).



--
This message was sent by Atlassian JIRA
(v6.1#6144)