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

Achim Nierbeck commented on KARAF-2818:
---------------------------------------

I think the two different configurations are still valid/usable and should 
remain in the way they are right now.
The o.a.k.features.cfg is as JB already stated for already registered features. 
My Idea of this Issue had been to add the ECF feature for convenience to the 
o.a.k.features.repos.cfg so that any user wanting to use it just needs to use 
the command: 
{code}
feature:repo-add ecf
{code}
and after that is happy with installing, as we have done with all the other 
features in the list, which are optional to include. 

Now for the MVN URL/Coordinates
{code}
cellar       = org.apache.karaf.cellar:apache-karaf-cellar:xml:features:(0,]
{code}
it is quite simple, it is the groupId:artifactId:type:classifier:version-range
for standard jar maven coordinate one can skip the type since it's clearly a 
jar, same is for war sometimes. 
Though if you add a features.xml from any maven coordinate you always need to 
use it fully-qualified, for example: 
{code}
features:repo-add 
mvn:org.apache.karaf.cellar/apache-karaf-cellar/xml/features/2.3.0
{code}

So why is it better to have a maven coordinate instead of having a html link, 
quite simple with that coordinate you define a way of telling the 
feature:repo-add command to search through the maven repository for exact this 
artifact but to look for the latest version. As the feature isn't under the 
control of Karaf and isn't a "main" feature it might have newer versions 
available so the user is eager to use the latest version. With this we give the 
user a convenient way of choosing the latest version available without actually 
knowing the exact location of the feature. 

> 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)

Reply via email to