[
https://issues.apache.org/jira/browse/KARAF-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675149#comment-16675149
]
Jean-Baptiste Onofré commented on KARAF-6000:
---------------------------------------------
The first idea is actually "dynamic" resource repositories (with dedicated
commands). Thanks for the explanation about resolving the deployment each time
we change the resource repositories set (adding/removing a repository).
About the "alternative to features", it's a rough idea, and I don't want to
fully remove feature. It's more to give some "OSGi closer" way to deal with
bundles/applications. I like the idea of command converting a features
repository as resource repository, eventually with verbose output. It would
give details about features values for users.
> 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)
