[
https://issues.apache.org/jira/browse/KARAF-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990835#comment-13990835
]
Scott lewis edited comment on KARAF-2818 at 5/6/14 5:15 PM:
------------------------------------------------------------
Just to continue discussion about this...I would argue that this thread
http://karaf.922171.n3.nabble.com/Karaf-3-0-1-how-to-avoid-usage-of-m2-repository-td4033016.html#a4033019
also supports my argument...given in comments above...that it should be
possible to use a non-maven repo for installing any karaf features...in all
contexts where it's appropriate (startup/config files as well as console and
webconsole...where it's already available).
I think that the discussion thread makes the case that this isn't something
that only karaf feature-providers (e.g. ECF) would like, but also something
that general users of karaf would also benefit from.
was (Author: scottslewis):
Just to continue discussion about this...I would argue that this thread
http://karaf.922171.n3.nabble.com/Karaf-3-0-1-how-to-avoid-usage-of-m2-repository-td4033016.html#a4033019
also supports my argument...given in comments above...that it should be
possible to use a non-maven repo for installing any karaf features...in all
contexts where it's appropriate (startup/config files as well as console and
webconsole...where it's already available).
I think that the discussion thread makes the case that this isn't something
that karaf feature-providers (e.g. ECF) would like, but also something that
general users of karaf would also benefit from.
> 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: 4.0.0, 3.0.2
>
>
> 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)
