[
https://issues.apache.org/jira/browse/KARAF-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674803#comment-16674803
]
Guillaume Nodet commented on KARAF-6000:
----------------------------------------
Not exactly sure to understand how far you want to go.
Adding / removing resource repository is not a problem. Currently, the
"globalRepository" is considered static, i.e. it's only read when the
features-core bundle is started. If we want to make is more dynamic and have
the ability to add / remove repositories at runtime, we need to ensure we
resolve the deployment again when a repository is removed / added, or that we
force the uninstallation of the resources that come from that repository in
order to make sure we always stay consistent.
About the "complete alternative to features": at runtime, a feature is
translated into a resource, but not a bundle resource, so we could translate a
feature repository into a resource repository very easily. That said, a lot of
things that are built into features can't be modelled just using bundles as
resources. I think one good thing would be to have a command that translate a
feature or a feature repository into a resource repository so that we can have
a better idea of how things are modelled and how verbose/complex it would be to
achieve the same without features (I'm thinking about conditionals, the
dependent flag, etc...).
> 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.2.2
>
>
> 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)
