Apparently it is just a blind copy and paste of play framework, and I don't see why it is necessary.
Play's logger.xml is used to mute some of its noisy dependencies, but reactivecouchbase's one is not doing anything meaningful other than adding up hazards of name collision.
In general, logging configuration should be left to application development/deployment and and a library should not alter it in any form, and that is the whole point of using slf4j.
Apparently it is just a blind copy and paste of play framework, and I don't see why it is necessary.
Play's logger.xml is used to mute some of its noisy dependencies, but reactivecouchbase's one is not doing anything meaningful other than adding up hazards of name collision.
In general, logging configuration should be left to application development/deployment and and a library should not alter it in any form, and that is the whole point of using slf4j.