[
https://issues.apache.org/jira/browse/ARIES-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592459#comment-14592459
]
Samuel Bratton commented on ARIES-1307:
---------------------------------------
Strange. I just reran the subsystems build with my patch in place and all tests
passed for me. The failures you reported above are what you'd see with the
MANIFEST.MF changes to the test bundles, but not the fix to
ImportPackageRequirement.java. Are you certain the whole patch was applied?
> 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)
