[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=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)
[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=15506931#comment-15506931 ] Christian Schneider commented on CXF-7060: -- In that case I would wait for the improved support and only then move the commands to gogo style. I would rather avoid having the code twice for now. > 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.3.4#6332)
[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=15506619#comment-15506619 ] Guillaume Nodet commented on CXF-7060: -- Until we can have full support for gogo commands in karaf, i'd rather provide both if plain gogo commands are actually needed. Such support (with help and completions) is doable, as I've done it inside the gogo-jline shell, but it's not integrated into karaf yet. > 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.3.4#6332)
[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=15506484#comment-15506484 ] Christian Schneider commented on CXF-7060: -- About the commands.. I wonder if we could switch to felix gogo commands. They should work reasonably well in karaf and would make us less dependent on the karaf version. We might loose some features (especially parameter auto complete) but that might be ok. WDYT? > 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.3.4#6332)
[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=15506209#comment-15506209 ] Guillaume Nodet commented on CXF-7060: -- One possibility would be to use the 1.3 namespace. I don't think we need to use any new feature from 1.4, so that should be fine. The benefit is that support for the 1.3 namespace has been added back into 2.4.3 and 3.0.4. We may want to keep commands separated though. Another option would be to use an xslt to generate the 1.0 version of the features.xml from the 1.3 version. > 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.3.4#6332)
[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=15506086#comment-15506086 ] Sergey Beryozkin commented on CXF-7060: --- Hi Guillaume, I had to start syncing between Karak and Karaf specific features: http://git-wip-us.apache.org/repos/asf/cxf/commit/44c608c2 I wonder if some features can be shared somehow... > 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.3.4#6332)
