aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-1863) Ensure type compatibility when running in an environment that already has bnd uses elsewhere
Date Fri, 16 Nov 2018 18:17:00 GMT

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

ASF subversion and git services commented on ARIES-1863:
--------------------------------------------------------

Commit 1846736 from rotty3000@apache.org in branch 'aries/trunk'
[ https://svn.apache.org/r1846736 ]

ARIES-1863 Ensure type compatibility when running in an environment that already has bnd uses
elsewhere

Signed-off-by: Raymond Auge <rotty3000@apache.org>

> 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)

Mime
View raw message