karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott lewis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-2818) Add ECF to feature repo
Date Fri, 14 Mar 2014 22:50:52 GMT

    [ https://issues.apache.org/jira/browse/KARAF-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13935767#comment-13935767

Scott lewis commented on KARAF-2818:

>Sorry, I should have been clearer, for adding it to the repos file I though more of the
>file then the features.cfg

My first comment is:   if an URL is accepted for a features repo everywhere else, why not
in o.a.k.features.repos.cfg?  That seems like a fixable bug to me.

And a question:  where is the o.a.k.features.repo.cfg syntax defined?...e.g.


ECF has an existing maven repo...but it doesn't have a set of features yet...mostly because
I can't find anyone that actually can say what the meta-data must look like to be readable
with the above syntax.  Pointers to specs and/or examples would be appreciated.

And a third question:   why two lists?...i.e. why o.a.k.features.cfg and o.a.k.features.repos.cfg?
 And if two...and URL syntax can't be supported in o.a.k.features.repos.cfg, why not also

My point is that *everywhere else* in Karaf an arbitrary URL is allowed except in o.a.k.features.repos.cfg.
  That seems strange to me...as obviously you are trying to allow consumers to install with
both maven repos and/or arbitrary URLs...and that seems like a good thing to me.

> 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

View raw message