[
https://issues.apache.org/jira/browse/KARAF-2818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936207#comment-13936207
]
Scott lewis commented on KARAF-2818:
------------------------------------
>I think the two different configurations are still valid/usable and should
>remain in the way they are right now.
I disagree. Look at it this way Achim: Every other part of Karaf's
provisioning mechanism is designed around letting Karaf consumers (users)
install via either a maven repo, or an arbitrary URL. This flexibility is a
good thing for consumers (and for runtime-independent framework
producers...like ECF, etc)...as it lets *them* jointly decide how to install
new karaf features into their Karaf runtime instance. I just see no reason to
arbitrarily take away that consumer flexibility for one part of the Karaf
configuration (o.a.k.features.repos.cfg).
Further, as I said...if you want to have separate cfg files for
features.repo.cfg (i.e. features.repo.url.cfg), but that seems kind of ugly to
me.
WRT MVN URL/Coordinates: Thanks for the description. Does a *specification*
of this syntax and it's implications for the maven metadata (pom, etc) even
exist?...perhaps alongside some usage examples? If so, could you please point
to where? (maven somewhere I presume).
WRT the feature versions...yes I understand the version range...but this
doesn't preclude having URL support alongside the maven identifier...and just
not supporting version ranges for URLs. There are many use cases where
version ranges are not needed...e.g. where the repo/URL is guaranteed by the
supplier to point to a single version...and so just add complexity. As an
example of this, the contents of my Karaf 3.0.0 o.a.k.features.repos.cfg
currently has *only* features with version range specifications of (0,]
...i.e. none of them are even providing useful version ranges anyway.
> 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)
