Re: Karaf Tooling maven plugin - karaf-maven-example-client - did not work as expected

[Jean-Baptiste Onofré]

Hi,

Just a quick update about this. The problem was not in the plugin but in 
the example.


I fixed it (see https://issues.apache.org/jira/browse/KARAF-6444).

Basically, as we introduced command ranking, the plugin configuration 
should be:



  bundle:list -t 0



Regards
JB

On 02/10/2019 21:20, stefang wrote:

Hell,

i am getting the following error when executing this example

[INFO] --- karaf-maven-plugin:4.3.0-SNAPSHOT:client (client) @
karaf-maven-example-client ---
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time:  2.074 s
[INFO] Finished at: 2019-10-02T19:32:27+02:00
[INFO]

[ERROR] Failed to execute goal
org.apache.karaf.tooling:karaf-maven-plugin:4.3.0-SNAPSHOT:client (client)
on project karaf-maven-example-client: Unable to parse configuration of mojo
org.apache.karaf.tooling:karaf-maven-plugin:4.3.0-SNAPSHOT:client for
parameter command: Cannot find default setter in class
org.apache.karaf.tooling.client.CommandDescriptor -> [Help 1]


Did i missed something ?
Other examples works as expected

Stefan




--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: Problem updating to 4.2.7

[Jean-Baptiste Onofré]

Hi David,

No problem. As the mailing list doesn't accept attachment, feel free to 
send to me directly.


Thanks

Regards
JB

On 30/10/2019 01:19, David Leangen wrote:

Thanks JB,

I’ll try to comb through the lists to figure out precisely what you mean by “a 
simple test”. Apologies for my ignorance… 

I’ll get back to you soon.


Cheers,
=David




On Oct 30, 2019, at 2:10, Jean-Baptiste Onofré  wrote:

Hi,

the easy path would be the features XML with a zip of your resources repository.

A simple test should be enough.

Thanks a lot !

Regards
JB

On 29/10/2019 11:13, David Leangen wrote:

Hi JB,

Sure! What would be the best way of doing that?

I could give you a reference to my docker image, config changes, and repo and 
you run it?

Or give you access to a running server instance?

Or something else?


Cheers,
=David




On Oct 29, 2019, at 17:45, Jean-Baptiste Onofré  wrote:

Hi David,

do you think you can have a simple test case you can send to me ?

It would help to identify the issues between 4.2.0 and 4.2.1.

Thanks,
Regards
JB

On 29/10/2019 09:29, David Leangen wrote:

4.2.1 was a no-go. The same problem occurred as with 4.2.7.

So it appears that the problematic change got introduced sometime between 4.2.0 
and 4.2.1.

For now, I will try to get my system up and running in 4.2.0 if I can figure 
out the resolution problems, but it would still be great to figure out why 
4.2.7 won’t start up…


Cheers,
=David




On Oct 29, 2019, at 17:15, David Leangen mailto:apa...@leangen.net>> wrote:


Hi,

FYI it looks like 4.2.0 worked. I am having trouble with resolution of my 
bundles now, but at least the problem I was seeing in 4.2.7 is not there.

I will give it a try with 4.2.1 next.


Cheers,
=David




On Oct 28, 2019, at 20:14, David Leangen mailto:apa...@leangen.net>> wrote:


The owner of the file (as well as the directory) is karaf.karaf.

 From /etc/passwd:

karaf:x:1001:1001::/home/karaf:/bin/bash


 From /etc/group:

karaf:x:1001:


The owner of the docker process in which karaf is running is root.


So I don’t think it’s a permissions problem.

The etc directory is mounted as a volume. It seems to be working fine (i.e. 
files can be changed both within the container and on the host).


Cheers,
=David




On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré mailto:j...@nanthrax.net>> wrote:

Hmmm,

does the user running Karaf has permission to read the file/folder ?

Regards
JB

On 28/10/2019 08:11, David Leangen wrote:

You amaze me! How are you so fast?

Anyway…

Again you’ll have to excuse my ignorance, but…

[root@deimos features]# pwd
/home/karaf/features
[root@deimos features]# ls
01-enroute.xml  03-base.xml 05-platform.xml  07-ddd.xml 09-app.xml integral.xml 
  ws.xml
02-patches.xml 04-bucketz.xml 06-web.xml   08-application.xml 
10-installation.xml  licensing.xml
[root@deimos features]#


Then:

karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
Adding feature url file:/home/karaf/features/01-enroute.xml
Error executing command: /home/karaf/features/01-enroute.xml (No such file or 
directory) : file:/home/karaf/features/01-enroute.xml
karaf@root()>


Cheers,
=David



On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré mailto:j...@nanthrax.net>> wrote:

Hi,

You can do:

feature:repo-add file:/path/to/your/features.xml

Then

feature:install -v -t enroute

Regards
JB

Create my own Whiteboard/Application with extensions

[Oleg Cohen]

Greetings,

I am using Aries HTTP Whiteboard in Karaf 4.2.7. All is working fine with
the default Whiteboard instance. I would like to create my own Jax-RS
Application with the same extensions that are configured in the default
Whiteboard, for example jaxb-json one. Is there a convenient way to clone
the default Whiteboard or create a fully-featured Application?

I would appreciate any guidance in this!

Thank you,
Oleg

Re: Problem updating to 4.2.7

[David Leangen]

Thanks JB,

I’ll try to comb through the lists to figure out precisely what you mean by “a 
simple test”. Apologies for my ignorance… 

I’ll get back to you soon.


Cheers,
=David



> On Oct 30, 2019, at 2:10, Jean-Baptiste Onofré  wrote:
> 
> Hi,
> 
> the easy path would be the features XML with a zip of your resources 
> repository.
> 
> A simple test should be enough.
> 
> Thanks a lot !
> 
> Regards
> JB
> 
> On 29/10/2019 11:13, David Leangen wrote:
>> Hi JB,
>> 
>> Sure! What would be the best way of doing that?
>> 
>> I could give you a reference to my docker image, config changes, and repo 
>> and you run it?
>> 
>> Or give you access to a running server instance?
>> 
>> Or something else?
>> 
>> 
>> Cheers,
>> =David
>> 
>> 
>> 
>>> On Oct 29, 2019, at 17:45, Jean-Baptiste Onofré  wrote:
>>> 
>>> Hi David,
>>> 
>>> do you think you can have a simple test case you can send to me ?
>>> 
>>> It would help to identify the issues between 4.2.0 and 4.2.1.
>>> 
>>> Thanks,
>>> Regards
>>> JB
>>> 
>>> On 29/10/2019 09:29, David Leangen wrote:
 4.2.1 was a no-go. The same problem occurred as with 4.2.7.
 
 So it appears that the problematic change got introduced sometime between 
 4.2.0 and 4.2.1.
 
 For now, I will try to get my system up and running in 4.2.0 if I can 
 figure out the resolution problems, but it would still be great to figure 
 out why 4.2.7 won’t start up…
 
 
 Cheers,
 =David
 
 
 
> On Oct 29, 2019, at 17:15, David Leangen  > wrote:
> 
> 
> Hi,
> 
> FYI it looks like 4.2.0 worked. I am having trouble with resolution of my 
> bundles now, but at least the problem I was seeing in 4.2.7 is not there.
> 
> I will give it a try with 4.2.1 next.
> 
> 
> Cheers,
> =David
> 
> 
> 
>> On Oct 28, 2019, at 20:14, David Leangen > > wrote:
>> 
>> 
>> The owner of the file (as well as the directory) is karaf.karaf.
>> 
>> From /etc/passwd:
>> 
>> karaf:x:1001:1001::/home/karaf:/bin/bash
>> 
>> 
>> From /etc/group:
>> 
>> karaf:x:1001:
>> 
>> 
>> The owner of the docker process in which karaf is running is root.
>> 
>> 
>> So I don’t think it’s a permissions problem.
>> 
>> The etc directory is mounted as a volume. It seems to be working fine 
>> (i.e. files can be changed both within the container and on the host).
>> 
>> 
>> Cheers,
>> =David
>> 
>> 
>> 
>>> On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré >> > wrote:
>>> 
>>> Hmmm,
>>> 
>>> does the user running Karaf has permission to read the file/folder ?
>>> 
>>> Regards
>>> JB
>>> 
>>> On 28/10/2019 08:11, David Leangen wrote:
 You amaze me! How are you so fast?
 
 Anyway…
 
 Again you’ll have to excuse my ignorance, but…
 
 [root@deimos features]# pwd
 /home/karaf/features
 [root@deimos features]# ls
 01-enroute.xml  03-base.xml 05-platform.xml  07-ddd.xml 09-app.xml 
 integral.xml   ws.xml
 02-patches.xml 04-bucketz.xml 06-web.xml   08-application.xml 
 10-installation.xml  licensing.xml
 [root@deimos features]#
 
 
 Then:
 
 karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
 Adding feature url file:/home/karaf/features/01-enroute.xml
 Error executing command: /home/karaf/features/01-enroute.xml (No such 
 file or directory) : file:/home/karaf/features/01-enroute.xml
 karaf@root()>
 
 
 Cheers,
 =David
 
 
> On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré  > wrote:
> 
> Hi,
> 
> You can do:
> 
> feature:repo-add file:/path/to/your/features.xml
> 
> Then
> 
> feature:install -v -t enroute
> 
> Regards
> JB

Re: Pluggable databases in apache karaf

[Steinar Bang]

> j...@nanthrax.net:

> I think you should take a look on pax-jdbc-config.

> It can simplify a lot your stuff.

It will certainly simplify this project (and make it less bound to
postgresql), and I will try it there:
 https://github.com/steinarb/sonar-collector

But for the projects that prompted the blog post there probably won't be
much gain (most of the code is releated to liquibase and I would have
had to have 3 OSGi bundles anyway (one for the schema, one for test data
and one for initial data i a production base), the code to connect to a
base is about the same number of lines as the config, so it would boil
down to a preference between code and config (where I usually land on
code), and in addition the database service proved a nice place to put
the SQL statements that are different between derby and PostgreSQL)
 https://github.com/steinarb/authservice
 https://github.com/steinarb/ukelonn
 https://github.com/steinarb/handlereg

(changing to pax-jdbc-config *would* make it simpler to use different
databases and re-use the liquibase scripts, e.g. use h2 for the test
database and MySQL for the production base, but having that flexibility
isn't important to me for these projects)

Re: Problem updating to 4.2.7

[Jean-Baptiste Onofré]

Hi,

the easy path would be the features XML with a zip of your resources 
repository.


A simple test should be enough.

Thanks a lot !

Regards
JB

On 29/10/2019 11:13, David Leangen wrote:

Hi JB,

Sure! What would be the best way of doing that?

I could give you a reference to my docker image, config changes, and repo and 
you run it?

Or give you access to a running server instance?

Or something else?


Cheers,
=David




On Oct 29, 2019, at 17:45, Jean-Baptiste Onofré  wrote:

Hi David,

do you think you can have a simple test case you can send to me ?

It would help to identify the issues between 4.2.0 and 4.2.1.

Thanks,
Regards
JB

On 29/10/2019 09:29, David Leangen wrote:

4.2.1 was a no-go. The same problem occurred as with 4.2.7.

So it appears that the problematic change got introduced sometime between 4.2.0 
and 4.2.1.

For now, I will try to get my system up and running in 4.2.0 if I can figure 
out the resolution problems, but it would still be great to figure out why 
4.2.7 won’t start up…


Cheers,
=David




On Oct 29, 2019, at 17:15, David Leangen mailto:apa...@leangen.net>> wrote:


Hi,

FYI it looks like 4.2.0 worked. I am having trouble with resolution of my 
bundles now, but at least the problem I was seeing in 4.2.7 is not there.

I will give it a try with 4.2.1 next.


Cheers,
=David




On Oct 28, 2019, at 20:14, David Leangen mailto:apa...@leangen.net>> wrote:


The owner of the file (as well as the directory) is karaf.karaf.

 From /etc/passwd:

karaf:x:1001:1001::/home/karaf:/bin/bash


 From /etc/group:

karaf:x:1001:


The owner of the docker process in which karaf is running is root.


So I don’t think it’s a permissions problem.

The etc directory is mounted as a volume. It seems to be working fine (i.e. 
files can be changed both within the container and on the host).


Cheers,
=David




On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré mailto:j...@nanthrax.net>> wrote:

Hmmm,

does the user running Karaf has permission to read the file/folder ?

Regards
JB

On 28/10/2019 08:11, David Leangen wrote:

You amaze me! How are you so fast?

Anyway…

Again you’ll have to excuse my ignorance, but…

[root@deimos features]# pwd
/home/karaf/features
[root@deimos features]# ls
01-enroute.xml  03-base.xml 05-platform.xml  07-ddd.xml 09-app.xml integral.xml 
  ws.xml
02-patches.xml 04-bucketz.xml 06-web.xml   08-application.xml 
10-installation.xml  licensing.xml
[root@deimos features]#


Then:

karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
Adding feature url file:/home/karaf/features/01-enroute.xml
Error executing command: /home/karaf/features/01-enroute.xml (No such file or 
directory) : file:/home/karaf/features/01-enroute.xml
karaf@root()>


Cheers,
=David



On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré mailto:j...@nanthrax.net>> wrote:

Hi,

You can do:

feature:repo-add file:/path/to/your/features.xml

Then

feature:install -v -t enroute

Regards
JB

Re: Problem updating to 4.2.7

[David Leangen]

Hi JB,

Sure! What would be the best way of doing that?

I could give you a reference to my docker image, config changes, and repo and 
you run it?

Or give you access to a running server instance?

Or something else?


Cheers,
=David



> On Oct 29, 2019, at 17:45, Jean-Baptiste Onofré  wrote:
> 
> Hi David,
> 
> do you think you can have a simple test case you can send to me ?
> 
> It would help to identify the issues between 4.2.0 and 4.2.1.
> 
> Thanks,
> Regards
> JB
> 
> On 29/10/2019 09:29, David Leangen wrote:
>> 
>> 4.2.1 was a no-go. The same problem occurred as with 4.2.7.
>> 
>> So it appears that the problematic change got introduced sometime between 
>> 4.2.0 and 4.2.1.
>> 
>> For now, I will try to get my system up and running in 4.2.0 if I can figure 
>> out the resolution problems, but it would still be great to figure out why 
>> 4.2.7 won’t start up…
>> 
>> 
>> Cheers,
>> =David
>> 
>> 
>> 
>>> On Oct 29, 2019, at 17:15, David Leangen >> > wrote:
>>> 
>>> 
>>> Hi,
>>> 
>>> FYI it looks like 4.2.0 worked. I am having trouble with resolution of my 
>>> bundles now, but at least the problem I was seeing in 4.2.7 is not there.
>>> 
>>> I will give it a try with 4.2.1 next.
>>> 
>>> 
>>> Cheers,
>>> =David
>>> 
>>> 
>>> 
 On Oct 28, 2019, at 20:14, David Leangen >>> > wrote:
 
 
 The owner of the file (as well as the directory) is karaf.karaf.
 
 From /etc/passwd:
 
 karaf:x:1001:1001::/home/karaf:/bin/bash
 
 
 From /etc/group:
 
 karaf:x:1001:
 
 
 The owner of the docker process in which karaf is running is root.
 
 
 So I don’t think it’s a permissions problem.
 
 The etc directory is mounted as a volume. It seems to be working fine 
 (i.e. files can be changed both within the container and on the host).
 
 
 Cheers,
 =David
 
 
 
> On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré  > wrote:
> 
> Hmmm,
> 
> does the user running Karaf has permission to read the file/folder ?
> 
> Regards
> JB
> 
> On 28/10/2019 08:11, David Leangen wrote:
>> 
>> You amaze me! How are you so fast?
>> 
>> Anyway…
>> 
>> Again you’ll have to excuse my ignorance, but…
>> 
>> [root@deimos features]# pwd
>> /home/karaf/features
>> [root@deimos features]# ls
>> 01-enroute.xml  03-base.xml 05-platform.xml  07-ddd.xml 09-app.xml 
>> integral.xml   ws.xml
>> 02-patches.xml 04-bucketz.xml 06-web.xml   08-application.xml 
>> 10-installation.xml  licensing.xml
>> [root@deimos features]#
>> 
>> 
>> Then:
>> 
>> karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
>> Adding feature url file:/home/karaf/features/01-enroute.xml
>> Error executing command: /home/karaf/features/01-enroute.xml (No such 
>> file or directory) : file:/home/karaf/features/01-enroute.xml
>> karaf@root()>
>> 
>> 
>> Cheers,
>> =David
>> 
>> 
>>> On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré >> > wrote:
>>> 
>>> Hi,
>>> 
>>> You can do:
>>> 
>>> feature:repo-add file:/path/to/your/features.xml
>>> 
>>> Then
>>> 
>>> feature:install -v -t enroute
>>> 
>>> Regards
>>> JB
 
>>> 
>> 

Re: Problem updating to 4.2.7

[Jean-Baptiste Onofré]

Hi David,

do you think you can have a simple test case you can send to me ?

It would help to identify the issues between 4.2.0 and 4.2.1.

Thanks,
Regards
JB

On 29/10/2019 09:29, David Leangen wrote:


4.2.1 was a no-go. The same problem occurred as with 4.2.7.

So it appears that the problematic change got introduced sometime 
between 4.2.0 and 4.2.1.


For now, I will try to get my system up and running in 4.2.0 if I can 
figure out the resolution problems, but it would still be great to 
figure out why 4.2.7 won’t start up…



Cheers,
=David



On Oct 29, 2019, at 17:15, David Leangen > wrote:



Hi,

FYI it looks like 4.2.0 worked. I am having trouble with resolution 
of my bundles now, but at least the problem I was seeing in 4.2.7 is 
not there.


I will give it a try with 4.2.1 next.


Cheers,
=David



On Oct 28, 2019, at 20:14, David Leangen > wrote:



The owner of the file (as well as the directory) is karaf.karaf.

From /etc/passwd:

karaf:x:1001:1001::/home/karaf:/bin/bash


From /etc/group:

karaf:x:1001:


The owner of the docker process in which karaf is running is root.


So I don’t think it’s a permissions problem.

The etc directory is mounted as a volume. It seems to be working 
fine (i.e. files can be changed both within the container and on the 
host).



Cheers,
=David



On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré > wrote:


Hmmm,

does the user running Karaf has permission to read the file/folder ?

Regards
JB

On 28/10/2019 08:11, David Leangen wrote:


You amaze me! How are you so fast?

Anyway…

Again you’ll have to excuse my ignorance, but…

[root@deimos features]# pwd
/home/karaf/features
[root@deimos features]# ls
01-enroute.xml  03-base.xml 05-platform.xml  07-ddd.xml 09-app.xml 
integral.xml   ws.xml
02-patches.xml 04-bucketz.xml 06-web.xml       08-application.xml 
10-installation.xml  licensing.xml

[root@deimos features]#


Then:

karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
Adding feature url file:/home/karaf/features/01-enroute.xml
Error executing command: /home/karaf/features/01-enroute.xml (No 
such file or directory) : file:/home/karaf/features/01-enroute.xml

karaf@root()>


Cheers,
=David


On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré > wrote:


Hi,

You can do:

feature:repo-add file:/path/to/your/features.xml

Then

feature:install -v -t enroute

Regards
JB

Re: Problem updating to 4.2.7

[David Leangen]

4.2.1 was a no-go. The same problem occurred as with 4.2.7.

So it appears that the problematic change got introduced sometime between 4.2.0 
and 4.2.1.

For now, I will try to get my system up and running in 4.2.0 if I can figure 
out the resolution problems, but it would still be great to figure out why 
4.2.7 won’t start up…


Cheers,
=David



> On Oct 29, 2019, at 17:15, David Leangen  wrote:
> 
> 
> Hi,
> 
> FYI it looks like 4.2.0 worked. I am having trouble with resolution of my 
> bundles now, but at least the problem I was seeing in 4.2.7 is not there.
> 
> I will give it a try with 4.2.1 next.
> 
> 
> Cheers,
> =David
> 
> 
> 
>> On Oct 28, 2019, at 20:14, David Leangen > > wrote:
>> 
>> 
>> The owner of the file (as well as the directory) is karaf.karaf.
>> 
>> From /etc/passwd:
>> 
>> karaf:x:1001:1001::/home/karaf:/bin/bash
>> 
>> 
>> From /etc/group:
>> 
>> karaf:x:1001:
>> 
>> 
>> The owner of the docker process in which karaf is running is root.
>> 
>> 
>> So I don’t think it’s a permissions problem.
>> 
>> The etc directory is mounted as a volume. It seems to be working fine (i.e. 
>> files can be changed both within the container and on the host).
>> 
>> 
>> Cheers,
>> =David
>> 
>> 
>> 
>>> On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré >> > wrote:
>>> 
>>> Hmmm,
>>> 
>>> does the user running Karaf has permission to read the file/folder ?
>>> 
>>> Regards
>>> JB
>>> 
>>> On 28/10/2019 08:11, David Leangen wrote:
 
 You amaze me! How are you so fast?
 
 Anyway…
 
 Again you’ll have to excuse my ignorance, but…
 
 [root@deimos features]# pwd
 /home/karaf/features
 [root@deimos features]# ls
 01-enroute.xml  03-base.xml   05-platform.xml  07-ddd.xml  
 09-app.xml integral.xml   ws.xml
 02-patches.xml 04-bucketz.xml  06-web.xml   08-application.xml 
 10-installation.xml  licensing.xml
 [root@deimos features]#
 
 
 Then:
 
 karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
 Adding feature url file:/home/karaf/features/01-enroute.xml
 Error executing command: /home/karaf/features/01-enroute.xml (No such file 
 or directory) : file:/home/karaf/features/01-enroute.xml
 karaf@root()>
 
 
 Cheers,
 =David
 
 
> On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré   >> wrote:
> 
> Hi,
> 
> You can do:
> 
> feature:repo-add file:/path/to/your/features.xml
> 
> Then
> 
> feature:install -v -t enroute
> 
> Regards
> JB
>> 
> 

Re: Problem updating to 4.2.7

[David Leangen]

Hi,

FYI it looks like 4.2.0 worked. I am having trouble with resolution of my 
bundles now, but at least the problem I was seeing in 4.2.7 is not there.

I will give it a try with 4.2.1 next.


Cheers,
=David



> On Oct 28, 2019, at 20:14, David Leangen  wrote:
> 
> 
> The owner of the file (as well as the directory) is karaf.karaf.
> 
> From /etc/passwd:
> 
> karaf:x:1001:1001::/home/karaf:/bin/bash
> 
> 
> From /etc/group:
> 
> karaf:x:1001:
> 
> 
> The owner of the docker process in which karaf is running is root.
> 
> 
> So I don’t think it’s a permissions problem.
> 
> The etc directory is mounted as a volume. It seems to be working fine (i.e. 
> files can be changed both within the container and on the host).
> 
> 
> Cheers,
> =David
> 
> 
> 
>> On Oct 28, 2019, at 17:17, Jean-Baptiste Onofré > > wrote:
>> 
>> Hmmm,
>> 
>> does the user running Karaf has permission to read the file/folder ?
>> 
>> Regards
>> JB
>> 
>> On 28/10/2019 08:11, David Leangen wrote:
>>> 
>>> You amaze me! How are you so fast?
>>> 
>>> Anyway…
>>> 
>>> Again you’ll have to excuse my ignorance, but…
>>> 
>>> [root@deimos features]# pwd
>>> /home/karaf/features
>>> [root@deimos features]# ls
>>> 01-enroute.xml  03-base.xml   05-platform.xml  07-ddd.xml  
>>> 09-app.xml integral.xml   ws.xml
>>> 02-patches.xml 04-bucketz.xml  06-web.xml   08-application.xml 
>>> 10-installation.xml  licensing.xml
>>> [root@deimos features]#
>>> 
>>> 
>>> Then:
>>> 
>>> karaf@root()> feature:repo-addfile:/home/karaf/features/01-enroute.xml
>>> Adding feature url file:/home/karaf/features/01-enroute.xml
>>> Error executing command: /home/karaf/features/01-enroute.xml (No such file 
>>> or directory) : file:/home/karaf/features/01-enroute.xml
>>> karaf@root()>
>>> 
>>> 
>>> Cheers,
>>> =David
>>> 
>>> 
 On Oct 28, 2019, at 16:04, Jean-Baptiste Onofré >>> >> wrote:
 
 Hi,
 
 You can do:
 
 feature:repo-add file:/path/to/your/features.xml
 
 Then
 
 feature:install -v -t enroute
 
 Regards
 JB
>