[
https://issues.apache.org/jira/browse/FELIX-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836138#action_12836138
]
Richard S. Hall commented on FELIX-2110:
----------------------------------------
But this is how the resolver works in the framework, we have an entity that has
a set of requirements associated with it, we don't just have requirements. I am
not keen to diverge from the approach of the framework resolver.
What we could possibly do to improve the user experience is to make some
utility methods for constructing a resource...this is something a JIRA issue
has asked for with respect to converting a bundle to a resource, so perhaps
there are a set of general utility methods around this area.
> 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.
