[
https://issues.apache.org/jira/browse/KARAF-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696433#comment-16696433
]
Grzegorz Grzybek commented on KARAF-6000:
-----------------------------------------
Not quite related, but {{etc/org.apache.karaf.features.xml}} contains the
_overrides_ which are strictly related to repository URIs + feature names/ids +
bundle URIs.
{{feature:refresh}} command re-reads this file and reprovisions all
requirements (still not related to _resources_) using what was already
implemented in _features service_.
Is this a plan to replace _karaf features_ with _OSGi R7 repositories_? I
remember there are many resolution quirks (blacklisting, overrides,
prerequisites) related to features which I don't think can be directly
translated to what _OSGi R7 repositories_ define.
> Add direct resource repositories support
> ----------------------------------------
>
> Key: KARAF-6000
> URL: https://issues.apache.org/jira/browse/KARAF-6000
> Project: Karaf
> Issue Type: New Feature
> Components: karaf
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 4.3.0
>
>
> Since OSGi R6, the "new" bundle repository spec allows to directly leverage
> any requirement/capability to do the bundle resolution.
> We already support this via the features (using {{resourceRepository}} with
> json or XML in {{etc/org.apache.karaf.features.cfg}}. I think it would be
> great to have a complete alternative to features using bundle repository. We
> could introduce a minimal feature set (just for the bootstrapping) as we have
> today, but delegating to {{etc/org.apache.karaf.repository.cfg}} for resource
> repositories and using them for resolution.
> We could also provide specific commands to manipulate the bundle repositories
> (like add, remove, as we have for features repositories).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
