[
https://issues.apache.org/jira/browse/FELIX-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840012#action_12840012
]
Richard S. Hall commented on FELIX-2144:
----------------------------------------
Yeah, I suppose that would work.
In reality, I am a little torn on this. The new approach I have for the
framework resolver uses double linking between capabilities and modules, since
it does simplify some aspects of the implementation (I also use double linking
between modules and bundles, but that is not relevant here). I do not, however,
use double linking between requirements and modules, although I thought about
doing it for consistency. I actually view the double linking as somewhat bad
form, but it really does help implementation-wise.
It is not 100% clear to me what we should do here.
I agree that the resolver doesn't really care about repositories and we could
just pass in one big array of all resources and not pass in any repositories to
it at all. Then this would solve this issue and clean things up quite a bit.
Personally, I think getting all resources from a repo as an array doesn't make
sense for efficiency purposes, but we have no choice given the Repository
interface. So making such a change would result in something that it not really
change the resolver algorithm at all. So, maybe that is the way we should go.
More long term, I think we should get back some sort of resource accessor
interface (like an immutable list) from the repos, but I think this approach
would still work with that too (i.e., we'd just pass in an accessor instead of
an array).
> Add global requirements and capabilities
> ----------------------------------------
>
> Key: FELIX-2144
> URL: https://issues.apache.org/jira/browse/FELIX-2144
> Project: Felix
> Issue Type: New Feature
> Components: Bundle Repository (OBR)
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: bundlerepository-1.6.0
>
>
> Global constraints on resources would be useful to be able to add constraints
> to the resolution like:
> * do not use a resource
> * add version range to used resources ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
