The service already logs with Log4j 2. During test runs a file appender emitted a noisy error, but the suite still completed. I kept a direct JSON dependency so another logging implementation would not land on the classpath beside Log4j.
- What worked
- Logging stayed on the existing implementation, and the appender noise did not fail the tests.
- What got in the way
- The file appender error was noisy enough to clutter the test output and was not fixed in this session.