Re: Can't uninstall shell-compat?

I agree that the error message could use some help here. I'll eventually build an assembly to set how 'help scr' is doing without shell-compat. On Mon, Sep 5, 2016 at 3:29 PM, Guillaume Nodet wrote: > The wording of the message is slightly wrong. > It should be "Feature

Re: Can't uninstall shell-compat?

The wording of the message is slightly wrong. It should be "Feature named 'shell-compat/4.0.6' is not required" but it would not be much more clear. In short, the fact that a feature is installed does not mean you can "uninstall" it. You can only uninstall features you have explicitly installed.

Re: Can't uninstall shell-compat?

You have a conditional feature that use it. What's your features set ? Regards JB On 09/05/2016 09:01 PM, Benson Margulies wrote: I install shell-compat by including 'standard' in my assembly. If I try to uninstall it, I get the following complaint that it is not installed.

Can't uninstall shell-compat?

I install shell-compat by including 'standard' in my assembly. If I try to uninstall it, I get the following complaint that it is not installed. karaf@root>feature:uninstall shell-compat/4.0.6 2016-09-05 14:59:20,611 | ERROR | nsole user karaf | ShellUtil | 191 -

Re: Is blueprint missing from the 'minimal' feature?

Stack trace for felix scr command NPE? in my experience the gogo annotations have to be loaded before scr in order for the “help” on the command to work, but I don’t recall an NPE. AFAICT to fix this (missing help) the scr gogo command would have to be in a separate bundle. thanks david

Re: Is blueprint missing from the 'minimal' feature?

Hmm. At one point, the Felix scr command NPE'd without shell-compat. I guess I'll try it again in 4.0.6. On the other hand, I'm probably stuck with blueprint sooner or later due to some other dependencies, so perhaps I should let this go. Thanks. benson On Mon, Sep 5, 2016 at 1:14 PM,

Re: Is blueprint missing from the 'minimal' feature?

shell-compat, via the shell 'console', depends on blueprint. Proof below. shell does not. Minimal includes shell, not shell-compat. This is sad, as shell-compat is required to make gogo commands work right. But it explains my confusion, as I thought that shell-compat was in 'minimal' and I was

Re: Is blueprint missing from the 'minimal' feature?

It's maybe because your bundles require blueprint (or a feature dependency), no ? If you use the karaf-service-maven-plugin with the Karaf shell annotations, it doesn't use blueprint. Regards JB On 09/05/2016 05:46 PM, Benson Margulies wrote: That error I sent is from karaf 4.0.6. it seems

Re: Is blueprint missing from the 'minimal' feature?

That error I sent is from karaf 4.0.6. it seems to me to be saying that the shell requires blueprint. Am I misreading it? On Sep 5, 2016 11:21 AM, "Jean-Baptiste Onofré" wrote: > Hi Benson, > > on Karaf 4, shell doesn't depend to blueprint anymore. > > Regards > JB > > On

Re: Is blueprint missing from the 'minimal' feature?

Hi Benson, on Karaf 4, shell doesn't depend to blueprint anymore. Regards JB On 09/05/2016 05:07 PM, Benson Margulies wrote: Achim, Yes, I understand the principle. What I don't understand is how anyone uses 'minimal'. Minimal includes shell, and shell requires blueprint, and blueprint isn't

Re: Is blueprint missing from the 'minimal' feature?

for Karaf 4, blueprint isn't required to be used for shell, therefore it's no requirement and works right away. Take a look here: https://github.com/ANierbeck/Karaf-Vertx/blob/master/Vertx-Karaf/pom.xml#L177-L178 This project also has custom shell commands, and doesn't need blueprint. regards,

Re: Is blueprint missing from the 'minimal' feature?

Achim, Yes, I understand the principle. What I don't understand is how anyone uses 'minimal'. Minimal includes shell, and shell requires blueprint, and blueprint isn't 'minimal'. Or is the idea that no one should try to use minimal, it's just a building block for standard and others? On Mon, Sep

Re: Is blueprint missing from the 'minimal' feature?

yep it's minimal so only the minimal required bundles are there. Blueprint is part of standard, as that isn't minimal anymore ... regards, Achiim 2016-09-05 16:45 GMT+02:00 Benson Margulies : > Folks, > > When I try to run an assembly that lists 'minimal' as a boot

Is blueprint missing from the 'minimal' feature?

Folks, When I try to run an assembly that lists 'minimal' as a boot feature, I get this error, indicating that (If I read it correctly) the shell requires blueprint. Is this intended? I can switch to 'standard' easily enough. 2016-09-05 10:42:36,560 | ERROR | pool-6-thread-1 |

Re: felix.fileinstall.enableConfigSave = false ignored?

Hi JB, jbonofre wrote > it depends how you use it: Karaf is responsible of the config store via > ConfigRepositoryImpl: > > https://github.com/apache/karaf/blob/master/config/src/main/java/org/apache/karaf/config/core/impl/ConfigRepositoryImpl.java > > So, disableConfigSave may not help. > >

Re: felix.fileinstall.enableConfigSave = false ignored?

Hi, it depends how you use it: Karaf is responsible of the config store via ConfigRepositoryImpl: https://github.com/apache/karaf/blob/master/config/src/main/java/org/apache/karaf/config/core/impl/ConfigRepositoryImpl.java So, disableConfigSave may not help. If you want to disable the Karaf

felix.fileinstall.enableConfigSave = false ignored?

Hello, For Karaf 4.0.6 I am trying to prevent changes made with the config:* commands to be persisted by setting the property felix.fileinstall.enableConfigSave = false in Karaf's $KARAF_HOME/etc/config.properties. But it appears the setting gets ignored. Whenever I issue a config:update the

Re: jdbc commands manual

karaf@root>version 4.0.5 karaf@root>jdbc:query sacomarDS "select count \(*\) from Mensajes" Error executing command jdbc:query: too many arguments specified karaf@root>jdbc:query sacomarDS "select count\(*\) from Mensajes" Error executing command jdbc:query: too many arguments specified

Re: jdbc commands manual

Which Karaf version ? Did you try to escape \( and \) ? Regards JB On 09/05/2016 01:37 PM, conejo wrote: The output: karaf@root>jdbc:query sacomarDS select count(*) from Mensajes COUNT(*) 6476 karaf@root>jdbc:query sacomarDS "select count(*) from Mensajes" Error executing command

Re: jdbc commands manual

The output: karaf@root>jdbc:query sacomarDS select count(*) from Mensajes COUNT(*) 6476 karaf@root>jdbc:query sacomarDS "select count(*) from Mensajes" Error executing command jdbc:query: too many arguments specified karaf@root>jdbc:query sacomarDS "select count (*) from Mensajes"

Re: jdbc commands manual

Can you paste the command with the quotes ? jdbc:query takes two arguments: the first one is the datasource name, the second one is the SQL query. Regards JB On 09/05/2016 12:58 PM, conejo wrote: Thanx. But now i get: Error executing command jdbc:query: too many arguments specified --

Re: jdbc commands manual

Hi, http://karaf.apache.org/manual/latest/#_datasources_jdbc You need to add quote between your query: jdbc:query myDs "select count (*) from messages where id < 100" Regards JB On 09/05/2016 12:51 PM, conejo wrote: Hi. Good Morning Is there a manual for jdbc commands? We do not know the

jdbc commands manual

Hi. Good Morning Is there a manual for jdbc commands? We do not know the sentences to be executed for obtain certain data. For example: jdbc:query myDs select count (*) from messages where id < 100 The cursor is left with the value '>' and you have to press CTRL + C to continue. Or jdbc:query

Re: Inject system property value via blueprint

Let me ping Grzegorz about that. Else I will take a look ;) Regards JB On 09/05/2016 10:44 AM, CLEMENT Jean-Philippe wrote: Ah yes, that Jira https://issues.apache.org/jira/browse/ARIES-1311 - Thank you Lichtin! The enhancement seems not to be planned for resolution. Is there a way to