[
https://issues.apache.org/jira/browse/FELIX-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12839838#action_12839838
]
Guillaume Nodet commented on FELIX-2144:
----------------------------------------
I see your point, but I think there is a problem. A repository is a bit more
than just an array of resources: it has a timestamp and a URL. In addition the
Resource can be used to retrieve its Repository using Resource#getRepository()
method, which kinda implies a Resource object can only be contained in a single
Repository (i'm not talking about having actual duplicate bundles of course).
So letting the user implement its own repository by simply wrapping an array of
Resource[] would lead to
repository.getResource()[0].getRepository() != repository
which should be avoided (or the api changed somehow).
Maybe removing the
Repository Resource#getRepository()
and adding a
void RepositotyAdmin#repository(Resource[] resources)
along with moving the isLocal() method from the Repository to the Resource
would work.
> 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.
