JIRA Report

TypeKeySummaryByStatusResolutionFix Version
WishLOG4J2-60Ability to configure log level filtering on a per <appender-ref/> basisRalph GoersResolvedFixed2.0-alpha1
BugLOG4J2-59test fail 2012 Mar 12Ralph GoersResolvedFixed2.0-alpha1
BugLOG4J2-56Level.toLevel throws IllegalArgumentException instead of returning default LevelRalph GoersClosedFixed
New FeatureLOG4J2-54Support existing ability to modify any of an event's fieldsRalph GoersResolvedFixed2.0-alpha1
New FeatureLOG4J2-53Better control over timestampRalph GoersResolvedFixed2.0-alpha1
BugLOG4J2-52'mvn test' requires initial 'mvn install'UnassignedResolvedFixed
BugLOG4J2-51ClassCastException in Category loggerRalph GoersClosedFixed
BugLOG4J2-50Incorrect %C output (FQCN)Ralph GoersClosedFixed
BugLOG4J2-49double message formatting w/SLF4JLoggerRalph GoersResolvedFixed
BugLOG4J2-48Throwables in ParameterizedMessageRalph GoersResolvedFixed0.1
New FeatureLOG4J2-32Create a Layout and SyslogAppender that support RFC 5424.Ralph GoersClosedFixed2.0-alpha1
New FeatureLOG4J2-31The Logging API should support a Message objectRalph GoersClosedFixed2.0-alpha1
WishLOG4J2-30Author tagsRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-27log4j 2 should implement the SLF4J API directlyRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-24Have an API method that does a deeper evaluation than Logger.isDebugEnabled() of whether logging will occurRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-23log4j 2.0 should work without an explicit configuration fileRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-21LoggingEvent message lost on serializationRalph GoersResolvedFixed2.0-alpha1
TestLOG4J2-20log4j 2 should have clean separation of configuration from functionRalph GoersResolvedFixed2.0-alpha1
ImprovementLOG4J2-19Provide looser coupling of PatternConvertersRalph GoersClosedFixed2.0-alpha1
New FeatureLOG4J2-17Provide enhanced logger filtering support.Ralph GoersClosedFixed2.0-alpha1
ImprovementLOG4J2-15Provide a "Proxy" Appender to support lazy initialization of Appenders.Ralph GoersClosedFixed2.0-alpha1
TaskLOG4J2-14log4j 2.0 development initationUnassignedClosedFixed0.1
WishLOG4J2-12log4j 2.0 should provide an API that is generally source compatible with log4j 1.2Ralph GoersResolvedFixed2.0-alpha1
WishLOG4J2-11log4j 2.0 should provide a log4j 1.2 emulation that is reasonably binary compatible with client applicationsRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-8log4j 2.0 should support recursionRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-7Java 5 idioms should be used in preference to earlier Java idiomsRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-6log4j 2.0 should support all capabilities of java.util.logging.Ralph GoersResolvedFixed2.0-alpha1
WishLOG4J2-5Appenders, Layouts and other back-end classes should be independent of logging APIRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-4Prefer java.nio to java.ioRalph GoersResolvedFixed2.0-alpha1
WishLOG4J2-3Minimal (aka fine grained) lockingRalph GoersResolvedFixed2.0-alpha1
ImprovementLOG4J2-1Custom rendering of exception associated with logging eventRalph GoersResolvedFixed2.0-alpha1