Ceki Gulcu | 88c4c45 | 2009-12-03 19:16:42 +0100 | [diff] [blame] | 1 | |
| 2 | The slf4j-migrator aims to |
| 3 | |
| 4 | General limitations |
| 5 | =================== |
| 6 | |
| 7 | - the FATAL level is not supported. |
| 8 | |
| 9 | This is limitation is not deemed serious because there are usually |
| 10 | very few log statements bearing the FATAL level. |
| 11 | |
| 12 | |
Craig P. Motlin | 4b710c8 | 2013-12-14 19:01:57 -0500 | [diff] [blame] | 13 | - if a method declares multiple loggers on the same line, the conversion will not be complete. Example: |
Ceki Gulcu | 88c4c45 | 2009-12-03 19:16:42 +0100 | [diff] [blame] | 14 | |
| 15 | |
| 16 | public void someMethod(Log l1, Log l2) { |
| 17 | ... |
| 18 | } |
| 19 | |
| 20 | will be converted as |
| 21 | |
| 22 | public void someMethod(Log l1, Logger l2) { |
| 23 | ... |
| 24 | } |
| 25 | |
| 26 | |
| 27 | When migrating from log4j |
| 28 | ========================= |
| 29 | |
| 30 | - Since NDC is not supported by SLF4J, the migrator cannot properly handle |
| 31 | NDC statements. |
| 32 | |
| 33 | - Calls to PropertyConfigurator or DomConfigurator cannot be migrated since |
| 34 | SLF4J the equivalents. |