THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
A log4j2 equivalent for traditional log4j config (connect-log4j2.properties) will be also provided, like other subprojects.
Add to this, the changes between log4j and log4j2 introduces the following changes:
- From log4j2, the name of the root logger becomes empty string from 'root'. It impacts Kafka connect's dynamic logging control feature. (And should be documented.)
- From log4j2, the logging level can't be null; GET `/admin/loggers` has been returning loggers with a non-null level (i.e., includes loggers with OFF level) but from log4j2, it returns the loggers with non-OFF levels only.
- If the user sets the root logger with PUT `/admin/loggers/{logger}`, all descendant loggers without the null level were affected. From log4j2, they will be affected since null level is regared as OFF level.
Like core, tThe test logging configuration (src/test/resources/log4j.properties) will be updated into log4j2, also.
4. Streams
Archetype log4j configuration will be updated into log4j2 equivalent (log4j2.properties).
...