You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Michal Hlavac (JIRA)" <ji...@apache.org> on 2017/11/06 10:50:01 UTC
[jira] [Commented] (CXF-7060) Provide Karaf 4 specific features and
commands
[ https://issues.apache.org/jira/browse/CXF-7060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240130#comment-16240130 ]
Michal Hlavac commented on CXF-7060:
------------------------------------
Line from this [changeset|https://github.com/apache/cxf/commit/3fbedf1397714824b9700cd4d49569087936fe1a#diff-f317dd8b5c6e2b464fc7873425dcb19b] that adds pax-cdi repository (line 21) has side effect, that it download pax-cdi version 1.0-SNAPSHOT. Karaf cannot resolve RC1 or RC2 version suffix.
Steps to reproduce:
# Downlod karaf and start karaf
# feature:list | grep pax-cdi
# feature:repo-add cxf 3.2.0
# feature:list | grep pax-cdi
> Provide Karaf 4 specific features and commands
> ----------------------------------------------
>
> Key: CXF-7060
> URL: https://issues.apache.org/jira/browse/CXF-7060
> Project: CXF
> Issue Type: Improvement
> Components: OSGi
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: 3.2.0
>
>
> There are a few shortcomings when using the existing features in Karaf 4.x.
> Creating specific features and commands will allow:
> * to not depend on blueprint
> * to validate the feature definitions correctly
> * fix existing features
> In addition some features have a strong dependency on jetty, while Karaf 4.1 will provide a choice for the http / war provider (jetty, tomcat, undertow), so it would make sense to refactor some features to better leverage those possibilities.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)