[
https://issues.apache.org/jira/browse/ARIES-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134138#comment-15134138
]
John Ross commented on ARIES-1446:
----------------------------------
The latest spec (R6) is the one to follow. The procedure for discovering
dependencies became less restrictive in order to maximize the probability of a
successful resolution. It gives the resolver more to work with for complex
resolutions that include uses constraints. A properly implemented resolver will
always honor the prioritized order when possible.
> ResolveContext should stop searching for capabilities once it found a match
> ---------------------------------------------------------------------------
>
> Key: ARIES-1446
> URL: https://issues.apache.org/jira/browse/ARIES-1446
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.6, subsystem-2.0.8
> Reporter: Bas
> Assignee: John Ross
> Labels: subsystem
>
> If I read the osgi.enterprise-5.0.0 spec correctly it says in section 134.6
> that searching for capabilities should stop once a repository returns
> results. The current resolvecontext does not do this but instead keeps on
> searching which might return results.
> Don't know if this causes behaviour that is not according to spec. but I can
> imagine that it might cause the resolver to have a more difficult time or it
> resolves to something that it should not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
