Installed/released runner does not work with logging

[TobiasNx]

Not sure since when this is a problem, but when changing the config/log4j.xml to debug in an installed/released runner and adding log-object in an example. Nothing seems to be logged.

examples/read/marc21/read-marc21.flux:

// opens file 'fileName', interprets the content as marc21 and writes to stdout

default fileName = FLUX_DIR + "10.marc21";

fileName|
open-file|
as-lines|
decode-marc21|
encode-formeta(style="multiline")|
log-object|
write("stdout");

Nothing is logged. I think that this was not an issue when fix was integrated into core. Is there some change between the integration and now that this may have broken the logging mechanisms.

[TobiasNx]

PS: It seems that release 7.0.0 already had this problem.

[TobiasNx]

Tested 6.1.2/6.2.0 of the released runner of core which still worked.

[TobiasNx]

Not sure what the problem is, but at my office computer it seems to work with the current released runner and installed runner 🤷‍♀️

[TobiasNx]

I have to correct myself. It seems that the DEBUG mode only works for fix, but not for metafacture-core in general.

If I use a fix this logs the syntax test of the fix.

// opens file 'fileName', interprets the content as marc21 and writes to stdout

default fileName = FLUX_DIR + "10.marc21";

fileName|
open-file|
as-lines|
decode-marc21|
fix("nothing()")|
encode-formeta(style="multiline")|
log-object|
write("stdout");

but not log-oject

[TobiasNx]

Maybe there is a conflict with the changes which we introduced with the log() function in fix?

[TobiasNx]

If I see it correctly we also do not have sufficient tests for the logging here:
https://github.com/metafacture/metafacture-core/tree/3ecc985c165ebc8505ac2fac9db4196644040f55/metafacture-monitoring/src/main/java/org/metafacture/monitoring