To investigate #1913 I first had to figure out how to configure logging and it turned out that the recently updated log4j was not configurable using our existing code paths! Doh! So ...
This fully replaces log4j with logback in DataCleaner. Log4j 2.x configuration is anyway not working as expected, so this was a good occasion to get fully rid of it and replace with logback which is much simpler and nicer too.
To investigate #1913 I first had to figure out how to configure logging and it turned out that the recently updated log4j was not configurable using our existing code paths! Doh! So ...
This fully replaces log4j with logback in DataCleaner. Log4j 2.x configuration is anyway not working as expected, so this was a good occasion to get fully rid of it and replace with logback which is much simpler and nicer too.