[
https://issues.apache.org/jira/browse/ARIES-1307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14593134#comment-14593134
]
David Bosschaert commented on ARIES-1307:
-----------------------------------------
Well I consistently get those failures (on mac OSX with Java 7) after applying
the patch:
{code}$ svn status
M
subsystem-core/src/main/java/org/apache/aries/subsystem/core/archive/ImportPackageRequirement.java
M subsystem-itests/src/test/bundles/tb1/META-INF/MANIFEST.MF
M subsystem-itests/src/test/bundles/tb2/META-INF/MANIFEST.MF{code}
Without your changes all is green.
[~tjwatson] would you have time to look at committing the patch maybe?
> 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)
