[
https://issues.apache.org/jira/browse/FELIX-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836337#action_12836337
]
Guillaume Nodet commented on FELIX-2110:
----------------------------------------
I do agree with the use of fake resources internally so as to not modify the
resolution algorithm at all.
However, I really think from a user point of view, creating fake resources is a
nonsense: that's not what the user want to express.
The use cases is not new (see FELIX-280, 3 years old).
I'm proposing to add the
void add(Requirement requirement)
Requirement[] getAddedRequirements()
methods on the Resolver and
Requirement requirement(String name, String filter) throws
InvalidSyntaxException;
on the RepositoryAdmin
THen the implementation can easily use a fake resource to hold the
requirements. We just need to make sure this resource is removed from all the
results. I don't honestly see the value in using a fake resource, but if you
wish to keep the resolution algorithm only deal with resources, i'm fine with
it.
> 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.
