OK, fair enough.
I created https://issues.apache.org/jira/browse/KARAF-7304 about that.
Regards
JB
> Le 23 déc. 2021 à 06:25, Paul Fraser a écrit :
>
> Hi JB,
>
> On 23/12/21 4:00 pm, Jean-Baptiste Onofre wrote:
>> Hi Paul
>>
>> Clean all are argument to karaf script doesn’t exist, only
Hi JB,
On 23/12/21 4:00 pm, Jean-Baptiste Onofre wrote:
Hi Paul
Clean all are argument to karaf script doesn’t exist, only clean exists. So
basically, doing ./bin/karaf clean or ./binn/karaf clean all is the same (all
is just ignored):
I looked in the script and could not see anything,
Hi Paul
Clean all are argument to karaf script doesn’t exist, only clean exists. So
basically, doing ./bin/karaf clean or ./binn/karaf clean all is the same (all
is just ignored):
https://github.com/apache/karaf/blob/main/main/src/main/java/org/apache/karaf/main/Main.java
karaf.clean.all
Hi,
Since the change to "bin/karaf clean" where the log is not cleaned, a
statement was made earlier in this group along the lines that "bin/karaf
clean all" was the way to produce the previous clean functionality.
This does not work and I have been unable to find the correct method.
Anyone
Hi,
The Karaf log command (log:set, log:get, log:list, etc) assumes that you use
log4j style configuration. It doesn’t support other configuration format.
However, you can still use log4j style configuration even if you use logback
service.
If you want that log:* commands support logback
Hi all,
caused by the known log4j2 vulnerability, I tried to switch from log4j to
logback.
I've updated the startup.properties and pax-logging configuration file and at
the first view it seems to work fine.
Unfortunately, when running any log command within the shell (e.g. log:display)
I
Hello JB,
thank you for your help!
The application is built with Java 8 and deploys fine if the Karaf
runtime is Java 11, but runs into the deployment issue if the Karaf
runtime is Java 8.
We specifically picked Karaf 4.2 as it is supposed to support Java 8.
And Camel 2.25 is Java 8 only
