[jira] [Updated] (ARIES-1307) mandatory matching directive on exported packages cause all importers to fail

["Samuel Bratton (JIRA)" <ji...@apache.org>]

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

Samuel Bratton updated ARIES-1307:
----------------------------------
    Attachment: ARIES-1307.patch

Modified code to add non-version attributes to ImportPackageRequirement. Modified subsystem-itests to fail without fix in place. Verified changes against R5 CT. 


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