aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Bosschaert (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARIES-1307) mandatory matching directive on exported packages cause all importers to fail
Date Thu, 18 Jun 2015 12:11:00 GMT

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

David Bosschaert updated ARIES-1307:
------------------------------------
    Fix Version/s: subsystem-core-2.0.1

> mandatory matching directive on exported packages cause all importers to fail
> -----------------------------------------------------------------------------
>
>                 Key: ARIES-1307
>                 URL: https://issues.apache.org/jira/browse/ARIES-1307
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>            Reporter: Thomas Watson
>            Assignee: David Bosschaert
>             Fix For: subsystem-core-2.0.1
>
>         Attachments: ARIES-1307.patch
>
>
> If you have subsystem that includes a resource with something like the following export:
> Export-Package: org.apache.felix.service.command; status=provisional; mandatory:=status
> And then another resource that correctly specifies the mandatory matching attribute like
the following:
> Import-Package: org.apache.felix.service.command; status=provisional
> The subsystems implementation will not allow the resource with the import package header
resolve to the package capability with the mandatory directive.
> This is because ImportPackageRequirement.ImportPackageRequirement(Clause, Resource) constructor
does not correctly handle the matching attributes of the clause.  The filter created only
has the packagename and if specified the package version range.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message