[
https://issues.apache.org/jira/browse/FELIX-4825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14350434#comment-14350434
]
Guillaume Nodet commented on FELIX-4825:
----------------------------------------
[~rickhall] The test case shows the problem. Let me explain it briefly...
The resource {{res2}} is the resource to resolve. With the current code, the
resolution leads to {{res5}} being wired to {{res6}} through an optional
requirement, while {{res6}} can not be resolved, because it has a mandatory
requirement on {{res3}}, which has a requirement with no matching capability.
The resource {{res6}} is also returned in the wiring map, but with no wires.
The problem seems to be related to optional requirements and cycles (there are
a lot of those in the small resource set). It may be possible to fix the
problem at the time the candidate is added to the localCandidateMap, but I
failed to see how to detect the problem (the resolution exception will be
thrown at a later time because of a cycle).
> The resolver may return wires to unresolved resources in some cases
> -------------------------------------------------------------------
>
> Key: FELIX-4825
> URL: https://issues.apache.org/jira/browse/FELIX-4825
> Project: Felix
> Issue Type: Bug
> Components: Resolver
> Affects Versions: resolver-1.0.0
> Reporter: Guillaume Nodet
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
