[
https://issues.apache.org/jira/browse/ARIES-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14596308#comment-14596308
]
Samuel Bratton commented on ARIES-1307:
---------------------------------------
I think the problem is that the susbsystem-itest pom still has a dependency on
the 1.3.0-SNAPSHOT org.apache.aries.subsystem.core rather than on the
2.0.1-SNAPSHOT jar which we just moved to.
> 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
> 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)
