[
https://issues.apache.org/jira/browse/FELIX-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836132#action_12836132
]
Guillaume Nodet commented on FELIX-2110:
----------------------------------------
Ok, I'll have a look, but this forces the user to actually implement Resource
and Requirement.
I don't really see the point in forcing the user doing so.
I think the resolver concept is not to resolve a set of resources, but to
resolve a set of requirements. If the requirement is
bundle:(&(symbolicname=xxx)(version=yyy))
then so be it.
But the use cases I had in mind is the an easy way to say "OBR, you're kinda
smart: give the set of bundles so that I can have this service". Or "What do
I have to deploy if I need the xxx package".
Currently, the loop is done a resource, but I think it would be cleaner to
resolve a requirement.
> The resolver should be able to resolve for some requirements in addition to
> resources
> -------------------------------------------------------------------------------------
>
> Key: FELIX-2110
> URL: https://issues.apache.org/jira/browse/FELIX-2110
> Project: Felix
> Issue Type: Improvement
> Components: Bundle Repository (OBR)
> Reporter: Guillaume Nodet
>
> For example if one want to resolve a given package.
> We could add
> void add(Requirement requirement);
> on the Resolver.
> Another way would be to create a fake resource with the requirement. This
> works as long as you don't want to actually install, because the resolver
> would then need a real resource. So in all cases, the resolver need to know
> about those resources, so it may be easier to let him create and handle those
> completely.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
