Re: [4.2.0.M1] - Startup failed

Thanks, let me take a look. Regards JB On 11/09/2017 07:00 AM, Francois Papon wrote: I tested using "cut" for evaluate the MAJOR_VERSION and it work's with bash, dash, sh : File bin/inc : method checkJvmVersion() line 218 MAJOR_VERSION=$("${JAVA}" -version 2>&1 \     |awk -F '"'

Re: [4.2.0.M1] - Startup failed

I tested using "cut" for evaluate the MAJOR_VERSION and it work's with bash, dash, sh : File bin/inc : method checkJvmVersion() line 218 MAJOR_VERSION=$("${JAVA}" -version 2>&1 \     |awk -F '"' '/version/ {print $2}' \     |cut -b 1)     if [ "${MAJOR_VERSION}" -ge "9" ]; then   

Re: [4.2.0.M1] - Startup failed

It's the substring method that it's not supported by dash and ksh, I change the header of the karaf.sh file to force the shell : !/bin/bash Le 09/11/2017 à 01:02, Francois Papon a écrit : > > This expression fail with dash but work with bash : > > line 218 and 268 in bin/inc > > if [

Re: [4.2.0.M1] - Startup failed

This expression fail with dash but work with bash : line 218 and 268 in bin/inc if [ "${MAJOR_VERSION:0:1}" -ge "9" ]; then Le 09/11/2017 à 00:27, Jean-Baptiste Onofré a écrit : > Weird. Let me double check. > > Regards > JB > On Nov 8, 2017, at 21:26, Francois Papon

Re: [4.2.0.M1] - Startup failed

I never change it, may be a Debian upgrade. But I work with other Karaf version Le 09/11/2017 à 00:23, Jean-Baptiste Onofré a écrit : > Bash is not your default shell ? > On Nov 8, 2017, at 21:22, Francois Papon > wrote: > >

Re: [4.2.0.M1] - Startup failed

Bash is not your default shell ? On Nov 8, 2017, 21:22, at 21:22, Francois Papon wrote: >I find a work around : > >|readlink -f $(which sh)/bin/dash sh ./bin/karaf don't work but bash >./bin/karaf work | > > >Le 09/11/2017 à 00:20, Jean-Baptiste Onofré a écrit : >>

Re: [4.2.0.M1] - Startup failed

I find a work around : |readlink -f $(which sh)/bin/dash sh ./bin/karaf don't work but bash ./bin/karaf work | Le 09/11/2017 à 00:20, Jean-Baptiste Onofré a écrit : > Let me try to reproduce. I'm using Oracle jdk. So let me try with openjdk. > > Regards > JB > On Nov 8, 2017, at 21:17, Francois

Re: [4.2.0.M1] - Startup failed

I just tested with bash and zsh. Continue to investigate. Regards JB On Nov 8, 2017, 21:20, at 21:20, "Jean-Baptiste Onofré" wrote: >Let me try to reproduce. I'm using Oracle jdk. So let me try with >openjdk. > >Regards >JB > >On Nov 8, 2017, 21:17, at 21:17, Francois Papon

Re: [4.2.0.M1] - Startup failed

Let me try to reproduce. I'm using Oracle jdk. So let me try with openjdk. Regards JB On Nov 8, 2017, 21:17, at 21:17, Francois Papon wrote: >I had tested on standard Debian shell, terminator and outside gnome >(tty) > > >Le 09/11/2017 à 00:09, Jean-Baptiste

Re: [4.2.0.M1] - Startup failed

I had tested on standard Debian shell, terminator and outside gnome (tty) Le 09/11/2017 à 00:09, Jean-Baptiste Onofré a écrit : > Hmm. What's the shell ? > > It works on my machines. > > Regards > JB > On Nov 8, 2017, at 21:03, Francois Papon

Re: [4.2.0.M1] - Startup failed

Hmm. What's the shell ? It works on my machines. Regards JB On Nov 8, 2017, 21:03, at 21:03, Francois Papon wrote: >Hi, > >When I launch Karaf I've got this error : > >./bin/karaf: 218: ./bin/karaf: Bad substitution > > >Karaf version : 4.2.0.M1 > >Karaf source :

[4.2.0.M1] - Startup failed

Hi, When I launch Karaf I've got this error : ./bin/karaf: 218: ./bin/karaf: Bad substitution Karaf version : 4.2.0.M1 Karaf source : download from Karaf website (http://www.apache.org/dyn/closer.lua/karaf/4.2.0.M1/apache-karaf-4.2.0.M1.tar.gz) Integrity check : ok I patch the ./bin/inc

RE: Need help resolving karaf 3.x dependency errors again

> -Original Message- > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] > Sent: Tuesday, November 07, 2017 8:56 PM > To: user@karaf.apache.org > Subject: Re: Need help resolving karaf 3.x dependency errors again > > Hi, > > Can you try to install the spring-aop feature provided by

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

I will open an issue. I had already implemented the workaround sugested and is working great. My question was more due to curiosity why a feature not using blueprint would trigger the installation of that bundle. Thank you. João Assunção Email: joao.assun...@exploitsys.com Mobile: +351

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

THis looks like a regression caused by KARAF-4932. Could you please raise a JIRA for this issue ? A workaround could be to modify the generation of you custom assembly so that the blueprint compatibility bundle is installed by default. At least, it would avoid the unwanted refresh of all

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

Of course The feature I'm trying to install: karaf@root()> feature:info paybox-io-modbus Feature paybox-io-modbus 0.1.0.SNAPSHOT Description: Modbus I/O implementation Feature has no configuration Feature has no configuration files Feature has no dependencies. Feature contains followed

Re: Why is org.apache.aries.blueprint.core.compatibility installed for some some features

Can you use feature:install --verbose --all-wiring and send us the output ? 2017-11-08 11:03 GMT+01:00 João Assunção : > Hello all, > > In Karaf 4.1.3 when I do a feature:install one of my features > the org.apache.aries.blueprint.core.compatibility bundle gets

Re: features being configured twice

Yes, the config blocks start like No, I don't start with any custom service configuration files in etc. Only the ones that come with Karaf. After running, however, configuration files for each of the services are created in etc (see the last paragraph in my original email). I did notice that

Re: Weird Exception Karaf 4.1.3 on startup

What about the terminal ? Regards JB On Nov 8, 2017, 13:57, at 13:57, Kevin Carr wrote: >Oh, this is on Linux with openjdk 1.8.144. > >On Nov 8, 2017 2:14 AM, "Jean-Baptiste Onofré" wrote: > >Hi Scott, > >Good catch. So, it only happens with when you

Re: Weird Exception Karaf 4.1.3 on startup

Can you share your os and terminal settings ? It works fine for me on Ubuntu. Regards JB On Nov 8, 2017, 13:56, at 13:56, Kevin Carr wrote: >It happens with both. With .start it seems to start fine. Then when I >ssh >I get the issue. > >With .karaf it is immediate due to

Re: Weird Exception Karaf 4.1.3 on startup

It happens with both. With .start it seems to start fine. Then when I ssh I get the issue. With .karaf it is immediate due to the terminal opening with the command. Seems to related to parse of history for the cli... On Nov 8, 2017 2:14 AM, "Jean-Baptiste Onofré" wrote:

Why is org.apache.aries.blueprint.core.compatibility installed for some some features

Hello all, In Karaf 4.1.3 when I do a feature:install one of my features the org.apache.aries.blueprint.core.compatibility bundle gets installed causing a refresh of all bundles and a Karaf shutdown. None of the bundles in the feature uses blueprint and the more exotic thing is that one of the

Re: Weird Exception Karaf 4.1.3 on startup

Hi Scott, Good catch. So, it only happens with when you start karaf with ./start only (not with ./karaf) ? I could be related to the terminal settings. Let me try to reproduce. Regards JB On 11/08/2017 06:31 AM, Kevin Carr wrote: Anyone understand what this exception is for? I get this as