Hi JB,
In previous emails to this list I have and also Matthias have reported
that 4.3.3 does not recognize the contents of the deploy directory
unless one of the files is touched or the features are copied into the
deploy folder.
This may be related to this problem and we await your check to confirm
or otherwise if there is a bug in fileinstall in 4.3.3 which is not
occurring in 4.3.2.
Paul
On 20/9/21 8:47 pm, Jean-Baptiste Onofre wrote:
Hi Paul,
It depends how you « Install » the bundles.
For instance, if you drop the bundles in the deploy folder, Karaf deployer will
« reinstall » them.
Regards
JB
Le 20 sept. 2021 à 12:34, Paul Fraser <pa...@qnenet.com> a écrit :
Hi,
If I use "bin/karaf debug clean" the active bundles are removed and the log
file is retained.
If I use "bin/karaf debug clean.all" the data file is removed but the active
bundles remain active.
I have also tried "cleanall" but in reading the jira I think clean.all is the
correct option .
Paul Fraser
On 19/9/21 3:05 pm, Jean-Baptiste Onofre wrote:
Hi Paul,
See https://issues.apache.org/jira/browse/KARAF-7146
Now a simple clean keep the log file. Cleanall removes all.
Regards
JB
Le 19 sept. 2021 à 01:09, Paul Fraser <pa...@qnenet.com> a écrit :
Hi,
With my installation of 4.3.3, when running Karaf with bin/karaf debug clean
the data cache is cleaned but the karaf log remains.
If I delete the data directory before running karaf, the log is a fresh one.
Anything changed in 4.3.3 that might cause this?
Paul Fraser
