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

Posted to dev@aries.apache.org by "Raymond Augé (JIRA)" <ji...@apache.org> on 2018/11/16 18:18:01 UTC

[jira] [Resolved] (ARIES-1863) Ensure type compatibility when running in an environment that already has bnd uses elsewhere

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

Raymond Augé resolved ARIES-1863.
---------------------------------
    Resolution: Fixed

> Ensure type compatibility when running in an environment that already has bnd uses elsewhere
> --------------------------------------------------------------------------------------------
>
>                 Key: ARIES-1863
>                 URL: https://issues.apache.org/jira/browse/ARIES-1863
>             Project: Aries
>          Issue Type: Improvement
>          Components: SPI Fly
>            Reporter: Raymond Augé
>            Assignee: Raymond Augé
>            Priority: Major
>             Fix For: spifly-1.2
>
>
> Due to how spifly now uses internal bnd types for header parsing it can occur that external implementation types come from some other occurrence of bnd. Make sure this doesn't blow up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)