Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0-beta9
-
None
-
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400)
Maven home: C:\Java\apache-maven-3.1.1\bin\..
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_51\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400) Maven home: C:\Java\apache-maven-3.1.1\bin\.. Java version: 1.7.0_51, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_51\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Description
The enum org.apache.logging.log4j.Level includes an intLevel property. This value was initially spaced by 1 for each level: 0, 1, 2 and so on. This change spaces the int by 100: 0, 100, 200, and so on.
This breaks binary compatibility (by behavior).
Ralph's suggestion: https://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201401.mbox/%3CD2FB152D-EAB9-4F01-AFE5-838A9AEFF68D@dslextreme.com%3E
Start of thread: https://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201401.mbox/%3cBD972E2F-C818-47BD-BB9E-168D52D5D980@nicholaswilliams.net%3e