[
https://issues.apache.org/jira/browse/KARAF-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935810#comment-13935810
]
Scott lewis commented on KARAF-2818:
------------------------------------
>I don't know if I'm clear
Your description is fine, but my impression is that the o.a.k.repos.cfg is
unnecessary. I.e. if you have to add the repo anyway...then why not have them
just add the repo (via webconsole URL or 'feature:repo-add <url>).
If o.a.k.feature.repos.cfg really needs to stay, I agree that it could/should
be either extended to support URL syntax, or another cfg added...e.g.
o.a.k.feature.repos.url.cfg...my preference would be for supporting URL syntax).
>The URL in feature repository is a MVN URL (I agree that it could be
>extended), supporting version range (to be >able to add the latest features
>repository).
Is there a specification of what this MVN URL syntax means?...in terms of the
expected/required maven meta-data? For example, what does having 'xml' or
'features' in the URL mean? (i.e. does it mean there's a reference to
karaf-features.xml somewhere in pom?...or does it mean there are <feature>
markup in top-level pom somewhere, or ?)
Thanks.
> Add ECF to feature repo
> -----------------------
>
> Key: KARAF-2818
> URL: https://issues.apache.org/jira/browse/KARAF-2818
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-config
> Affects Versions: 3.0.0
> Reporter: Achim Nierbeck
> Assignee: Achim Nierbeck
> Fix For: 3.0.1, 3.1.0
>
>
> Eclipse communication framework (ECF) now provides a feature file for easier
> installation in Karaf. The link to the repository should be included in the
> features.repo.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
