Do not give deprecation warning when converterClass and class are both specified in conversionRule (original) (raw)

The code should not give a deprecation warning if both converterClass and class tags are given in a conversionRule tag. Instead, it should silently ignore the superfluous converterClass and use the value of class.

Generally, unknown or unsupported tags in the configuration XML should be silently ignored - certainly not raise deprecation warnings. That is counter to the general use of XML.

The code should, to facilitate backward compatibility, allow for both tags to be present. If a user uses older logback, then the same XML will cause converterClass to be used, while newer version will use the class.

Yours,
Christian