Repository: logging-log4j2
Updated Branches:
  refs/heads/master d82dba5d8 -> a83e006bc


Prepare for release


Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo
Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/a83e006b
Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/a83e006b
Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/a83e006b

Branch: refs/heads/master
Commit: a83e006bc4504b7f555cc3f9813f9da9c3ddae2c
Parents: d82dba5
Author: rgoers <[email protected]>
Authored: Sun Feb 22 15:05:39 2015 -0700
Committer: rgoers <[email protected]>
Committed: Sun Feb 22 15:05:39 2015 -0700

----------------------------------------------------------------------
 RELEASE-NOTES.txt           | 294 +++++++--------------------------------
 src/changes/announcement.vm | 185 ++----------------------
 src/changes/changes.xml     |   4 +-
 3 files changed, 59 insertions(+), 424 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/a83e006b/RELEASE-NOTES.txt
----------------------------------------------------------------------
diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt
index 2f4f883..3478944 100644
--- a/RELEASE-NOTES.txt
+++ b/RELEASE-NOTES.txt
@@ -1,266 +1,70 @@
 
-              Apache Log4j 2.1 RELEASE NOTES
+              Apache Log4j 2.2 RELEASE NOTES
 
-The Apache Log4j 2 team is pleased to announce the Log4j 2.1 release!
+The Apache Log4j 2 team is pleased to announce the Log4j 2.2 release!
 
 Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
 Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
+many other modern features such as support for Markers, property substitution 
using Lookups, and asynchronous
+Loggers. In addition, Log4j 2 will not lose events while reconfiguring.
 
-This is the fourth GA release which contains several bugfixes and new 
features. There are two
-new Maven artifacts in this release: log4j-jul and log4j-iostreams. Both 
components are API-based
-with optional Core features.
+This is the fifth GA release. It contains several bugfixes and new features.
 
-GA Release 2.1
+GA Release 2.2
 
 Changes in this version include:
 
 New features:
-[LOG4J2-868]  Add ShutdownCallbackRegistry interface for customizable shutdown 
callback handling. This is particularly
-              useful for application servers that wish to integrate with Log4j 
2. 
-[LOG4J2-589]  Supported filtering on custom log levels in configuration. 
-[LOG4J2-856]  Documentation] add sections on the JUL Adapter, IO Streams and 
NoSQL Appenders to the Maven and Ivy page. 
-[LOG4J2-848]  Add a Java lookup to provide nicely formatted runtime version 
information. 
-[LOG4J2-809]  Move reflection utility class to API's private utility classes. 
-[LOG4J2-833]  Documentation] added Runtime Dependencies link to left nav-bar 
on site. 
-[LOG4J2-816]  Documentation] added section on XInclude to user manual 
Configuration page. 
-[LOG4J2-547]  Add the Log4j IOStreams component. 
-[LOG4J2-431]  Added Memory-Mapped File Appender. Thanks to Claude Mamo. 
-[LOG4J2-827]  Support use of TypeConverter classes through the standard Plugin 
system. 
-[LOG4J2-825]  Add simple validation constraint annotations for the Plugin 
system. 
-[LOG4J2-428]  Implement a GELF layout. Thanks to Mark Paluch, Mikael 
St�ldal. 
-[LOG4J2-608]  Add java.util.logging implementation based on log4j-api. See 
log4j-jul documentation for more details. 
-[LOG4J2-793]  Add support for custom SLF4J Markers in log4j-slf4j-impl module. 
-[LOG4J2-771]  Add lookup for application main arguments. 
-[LOG4J2-787]  Add lookup for JVM arguments. 
+o LOG4J2-941:  Allow JSON layout to create one compact log record per line. 
Thanks to Konstantinos Liakos. 
+o LOG4J2-933:  HTML layout should not use attribute minimalization for hr 
noshade. Thanks to ppiman at gmail.com. 
+o LOG4J2-895:  Specify the SyslogAppender connect timeout value as part of the 
configuration.
+        The SyslogAppender takes a new parameter connectTimeoutMillis. 
+o LOG4J2-899:  Specify the SocketAppender connect timeout value as part of the 
configuration.
+        The SyslogAppender takes a new parameter connectTimeoutMillis. 
 
 Fixed Bugs:
-[LOG4J2-676]  Some typo fixes and enhancements for the site. Thanks to Stefan 
Bodewig. 
-[LOG4J2-866]  Documentation] fixed missing closing parenthesis in code 
example. Thanks to Gerard Weatherby. 
-[LOG4J2-862]  Fixed classloader issue that prevented Log4j from finding the 
implementation when used in a custom Ant task. Thanks to Michael Sutherland. 
-[LOG4J2-861]  Documentation] fix broken links on left navigation Extending 
Log4j Configuration sub-menu. 
-[LOG4J2-797]  Documentation] clarified why log4j-core is a compile time 
dependency in Maven and Ivy page. Thanks to Andreas Rytina. 
-[LOG4J2-855]  Documentation] fix broken links on Appenders manual page. 
-[LOG4J2-807]  Prevent NPE when configuration with AsyncLogger/AsyncRoot is 
reloaded. 
-[LOG4J2-678]  Documentation] fixed minor issues with Log4j2 web 
site/documentation. Thanks to Matt Sicker. 
-[LOG4J2-843]  Migrate JpaHyperSqlAppenderTest JUnit performance test to 
log4j-perf. 
-[LOG4J2-842]  Migrate JpaH2AppenderTest JUnit performance test to log4j-perf. 
-[LOG4J2-841]  Migrate JdbcHyperSqlAppenderTest JUnit performance test to 
log4j-perf. 
-[LOG4J2-840]  Migrate JdbcH2AppenderTest JUnit performance test to log4j-perf. 
-[LOG4J2-830]  Respect external interrupt signal to allow application shutdown 
after joining AsyncAppender thread. 
-[LOG4J2-813]  MarkerManager Log4jMarker.hasParents() returns opposite of 
correct result. Thanks to David Erichsen, Brandon Barry. 
-[LOG4J2-785]  Documentation] fixed capitalization inconsistency in user manual 
example config. 
-[LOG4J2-829]  Fixed issue in RollingFile filePattern] backslashes are path 
separators, not escape characters. 
-[LOG4J2-832]  ThrowableProxy fails if a class in logged stack trace throws 
java.lang.Error from initializer Thanks to Seth Leger. 
-[LOG4J2-745]  Avoid ConverterKey plugin clashes by using a more predictable 
plugin loading infrastructure.
-              Plugins have been segmented int[three parts] class path, 
user-specified packages, and OSGi bundles. Thanks to Scott Harrington. 
-[LOG4J2-798]  Fixed plugin scanning redundancy causing massive slowdowns in 
certain environments. Thanks to Scott Harrington. 
-[LOG4J2-753]  Reduced CachedClock thread contention. 
-[LOG4J2-819]  Fixed memory leak in Tomcat 6 caused by clock background threads 
unintentionally
-              started by Tomcat after web application stop. Thanks to Gary 
Gregory. 
-[LOG4J2-391]  FlumePersistentManager now handles LockConflictExceptions in 
Berkeley Db when sending a batch. Thanks to Kamal Bahadur. 
-[LOG4J2-782]  Remove invalid Oracle Maven repository. 
-[LOG4J2-796]  Fixed issue where log4j-to-slf4j did not work correctly with 
SLF4J Simple Logger. 
-[LOG4J2-811]  SimpleLogger throws ArrayIndexOutOfBoundsException for an empty 
array. Thanks to Yogesh Rao. 
-[LOG4J2-663]  Fix OSGi Import-Package problem with the JMS API. Thanks to 
Florian Brunner. 
-[LOG4J2-783]  PatternLayout should use platform character encoding by default, 
not UTF-8. Thanks to Minglei Lee. 
+o LOG4J2-938:  (JMX) To avoid memory leaks when web applications are 
restarted, JMX notifications are sent from
+        the caller thread in web applications. For non-web applications 
notifications are sent from a background thread
+        as before. Thanks to Mauro Molinari. 
+o LOG4J2-957:  Missing toUpperCase("Locale.ENGLISH"). Thanks to fatih 
guleryuz. 
+o LOG4J2-956:  Manual refers to Route "AppenderRef" attribute, should be 
"ref". Thanks to David Kellerman. 
+o LOG4J2-944:  Log4j Flume appender is not adding millisecond to the event 
headers when the event is logged at 000 milliseconds. Thanks to Vinayaka 
Ramachandra. 
+o LOG4J2-924:  Log4j 1.2 Bridge doesn't map level ALL correctly in 
Category.getEffectiveLevel(). Thanks to Ryan Rupp. 
+o LOG4J2-931:  ConsoleAppender is missing @PluginFactory annotation at 
createAppender method. Thanks to Robert Gacki. 
+o LOG4J2-919:  Logging system fails to initialize if XInclude API is not 
available. Thanks to David Johle. 
+o LOG4J2-914:  ThrowableProxy.getExtendedStackTraceAsString causes 
NullpointerException. Thanks to Kaj Bjurman. 
+o LOG4J2-912:  XML configuration does not report full error message for 
XInclude parser configuration problems. 
+o LOG4J2-903:  ClassLoaderContextSelector uses ClassLoader.toString() as a key 
Thanks to Mauro Molinari. 
+o LOG4J2-834:  ThrowableProxy throws NoClassDefFoundError. Thanks to Nikita 
Koval, Leonard Broman, Thiago Kronig. 
+o LOG4J2-893:  NullPointerException on filter when mapping JUL to Log4j2. 
+o LOG4J2-892:  JUL adapter does not map Log4j'2 FATAL level to a JUL level. 
+o LOG4J2-881:  AbstractLifecycle should not implement equals() and hashCode(). 
Thanks to Mariano Gonzalez. 
+o LOG4J2-897:  Javadoc for org.apache.log4j.BasicConfigurator.configure() is 
incorrect. 
+o LOG4J2-891:  AbstractLifecycle should not implement equals() and hashCode(). 
+o LOG4J2-946:  [docs] Using Log4j 2 in Web Applications: Update example 
(Log4jWebLifeCycle is not visible). Thanks to artemonster. 
 
 Changes:
-[LOG4J2-845]  Add 2.1.0 to compatible versions in Log4j API ProviderUtil and 
update Log4jAPIVersion to 2.1.0 in
-              core META-INF/log4j-provider.properties. 
-[LOG4J2-844]  Update JMH to 1.1 from 0.7.2. 
-[LOG4J2-831]  Documentation] updated FAQ "which jars" diagrams for JUL bridge 
and 2.1 version. 
-[LOG4J2-780]  Update Spring Framework to 3.2.11.RELEASE from 3.2.8.RELEASE. 
-[LOG4J2-815]  Unify the two JMS appenders into a single appender. 
Configurations written for 2.0 will still work in 2.1+. 
-[LOG4J2-790]  Update Jackson to 2.4.2 from 2.4.1 (for XML and JSON 
processing). 
-[LOG4J2-766]  Incomplete documentation for JSONLayout. Thanks to Bruno P. 
Kinoshita. 
-[LOG4J2-800]  All life cycle implementations should be serializable.
-              This is still work in progress. 
-[LOG4J2-801]  org.apache.logging.log4j.core.Logger should be serializable.
-              This is still work in progress. 
-[LOG4J2-810]  Update javax.mail to 1.5.2 from 1.5.0. 
-[LOG4J2-822]  Update org.eclipse.persistence.jpa to 2.5.2 from 2.5.1. 
-[LOG4J2-867]  FlumeAppender] maxDelay not in seconds, but milliseconds.
-              Add time scale to some settings, for example maxDelayMillis 
instead of maxDelay.
-              The old names are aliased for compatibility. 
-
-
-Apache Log4j 2.1 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
-very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
-org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
-
-For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
-patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
-
-http://logging.apache.org/log4j/2.x/
-
--------------------------------------------------------------------------------
-
-              Apache Log4j 2.0.2 RELEASE NOTES
-
-The Apache Log4j 2 team is pleased to announce the Log4j 2.0.2 release!
-
-Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
-Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
-
-This is the third GA release which contains several bugfixes from the previous 
release.
-
-Bug fixes and enhancements
-
-Changes in this version include:
-
-
-Fixed Bugs:
-[LOG4J2-773]  Site] log4j-core component pages were still using the old logo.
-[LOG4J2-760]  Documentation improvement] link to dependency tree from 
log4j-core component page,
-              link to log4j-core component page from FAQ page.
-[LOG4J2-679]  Resolved race condition that caused log file rotation to fail 
with error] "Unable to create directory ..."
-[LOG4J2-726]  Prevent application from hanging when PatternLayout 
configuration has opening '{' but no closing '}'.
-[LOG4J2-769]  Startup takes a long time if you have empty packages attribute. 
Thanks to Scott Harrington.
-[LOG4J2-763]  Improved asynchronous loggers and appenders to ensure the 
formatted message does not change even if
-              parameters are modified by the application. 
(ParameterizedMessage was already safe.)
-              Improved documentation. Thanks to Stephen Connolly.
-[LOG4J2-729]  Emit warning message to console if no configuration file found.
-[LOG4J2-765]  Improve warning message when missing log4j-core in the classpath.
-[LOG4J2-722]  Clarified in documentation that Commons Logging jar is required 
when using log4j-jcl.
-[LOG4J2-723]  Clarified in documentation that SLF4J API jar is required when 
using log4j-slf4j-impl.
-[LOG4J2-759]  Fixed various minor site/documentation issues, mostly versioning 
related.
-[LOG4J2-756]  Prevent JUnit test from creating unnecessary Log4j2Plugins.dat 
during build. Thanks to Scott Harrington.
-
-Changes:
-[LOG4J2-775]  Update Apache Flume to 1.5.0.1 from 1.5.0.
-[LOG4J2-730]  Allow Log4jContextFactory subclasses to specify a custom 
ContextSelector.
-
-
-Apache Log4j 2.0.2 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
-very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
-org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
-
-For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
-patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
-
-http://logging.apache.org/log4j/2.x/
-
--------------------------------------------------------------------------------
-
-              Apache Log4j 2.0.1 RELEASE NOTES
-
-The Apache Log4j 2 team is pleased to announce the Log4j 2.0.1 release!
-
-Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
-Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
-
-This is the first GA release, after thirteen prior releases over the last 4 
years.
-
-?
-
-Changes in this version include:
-
-New features:
-[LOG4J2-725]  Added WebLoggerContextUtils class to log4j-web for helper 
methods useful for asynchronous servlets.
-[LOG4J2-710]  Added documentation for Custom Levels and Custom Loggers.
-
-Fixed Bugs:
-[LOG4J2-744]  Avoid unnecessary Clock calls when TimestampMessage is logged. 
Thanks to Scott Harrington.
-[LOG4J2-704]  Improved error message if configuration file not found.
-[LOG4J2-750]  Webapp configuration page has incorrect class name. Thanks to 
Mike Calmus.
-[LOG4J2-749]  Retain the default date pattern after fixing the ISO8601 
pattern. Thanks to Scott Harrington.
-[LOG4J2-670]  DatePatternConverter ISO8601_PATTERN now conforms to ISO8601.
-[LOG4J2-741]  Reinstate the package configuration attribute for discovering 
custom plugins.
-[LOG4J2-742]  XInclude not working with relative path. Thanks to Pascal 
Chollet.
-[LOG4J2-740]  Fixed typo in webapp manual regarding sample web.xml file. 
Thanks to Kosta Krauth.
-[LOG4J2-738]  RollingFileManager deadlock if async action thread fails to 
start. Thanks to Timothy Stack.
-[LOG4J2-736]  Fixed log4j-bom so that it won't specify a default scope on any 
third party dependencies.
-[LOG4J2-735]  Fixed log4j-bom so that it won't interfere with spring-bom and 
others.
-[LOG4J2-731]  Updated documentation regarding extensions to 
LoggerContextFactory and Log4j 2 providers.
-[LOG4J2-373]  Fixed ClassLoader issues in loading Log4j providers in an OSGi 
environment.
-[LOG4J2-719]  Correctly handle NetworkOnMainThreadException thrown on Android 
during Log4j2 initialization.
-[LOG4J2-716]  Automatically disable log4j JMX when detecting we are running on 
Android.
-[LOG4J2-657]  Fixed AbstractDatabaseManager to close connection on 
writeInternal error. Thanks to Stefan Wehner.
-[LOG4J2-713]  Android: java.lang.VerifyError] 
org/apache/logging/log4j/core/util/Closer Thanks to Nelson Melina.
-[LOG4J2-703]  Android] Could not find class 'javax.naming.InitialContext', 
referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup. 
Thanks to Nelson Melina.
-
-
-
-Apache Log4j 2.0.1 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
+o LOG4J2-955:  Documentation: clarify system properties to control status 
logger, improve troubleshooting FAQ entry. 
+o LOG4J2-950:  Incorrect attribute name in PropertiesRewritePolicy example. 
Thanks to Joel Edwards. 
+o LOG4J2-901:  Update docs for SyslogAppender: "No structured id name was 
supplied" Thanks to Tihomir Meščić, Siegfried Greisinger. 
+o LOG4J2-958:  Update from Jackson 2.5.0 to 2.5.1. 
+o LOG4J2-925:  Update from Jackson 2.4.4 to 2.5.0. 
+o LOG4J2-910:  Update Jackson from 2.4.3 to 2.4.4. 
+o LOG4J2-881:  Update Jackson from 2.4.2 to 2.4.3. 
+o LOG4J2-882:  Update maven-core from 3.1.0 to 3.2.3. 
+o LOG4J2-883:  Update tests from org.apache.felix.framework 4.2.1 to 4.4.1. 
+o LOG4J2-884:  Update org.eclipse.osgi from 3.6.0 to 3.7.1. 
+o LOG4J2-900:  Update Apache Flume from 1.5.0.1 to 1.5.2. 
+
+
+Apache Log4j 2.2 requires a minimum of Java 6 to build and run. Future 
releases may require a minimum
+of Java 7.
+
+Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api 
component, however it does not implement some of the
 very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
 org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
 
 For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
 patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
 
-http://logging.apache.org/log4j/2.x/
-
--------------------------------------------------------------------------------
-
-              Apache Log4j 2.0 RELEASE NOTES
-
-The Apache Log4j 2 team is pleased to announce the Log4j 2.0 release!
-
-Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
-Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
-
-This is the first GA release, after thirteen prior releases over the last 4 
years.
-
-GA Release
-
-Changes in this version include:
-
-New features:
-[LOG4J2-519]  Added support for generating custom logger wrappers that replace 
the existing log levels
-        and extended logger wrappers that add custom log levels to the 
existing ones.
-[LOG4J2-696]  RegexFilter does not match multiline log messages.
-
-Fixed Bugs:
-[LOG4J2-705]  Fixed issue where Async Logger does not log thread context stack 
data.
-              API change: added method getImmutableStackOrNull() to 
ThreadContext.ContextStack interface.
-[LOG4J2-631]  Update docs to clarify how to use formatter logger and standard 
logger together.
-[LOG4J2-441]  LoggerConfigs with no Level now inherit the Level from their 
parent.
-[LOG4J2-703]  Android] Could not find class 'javax.naming.InitialContext', 
referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup. 
Thanks to Nelson Melina.
-[LOG4J2-699]  PatternLayout manual page missing documentation on header/footer.
-[LOG4J2-625]  Fixed Serialization error with SocketAppender and Async Loggers.
-              (Fixed in RC2, but wasn't included in release notes.)
-[LOG4J2-538:  JMX GUI] fixed occasional ArrayIndexOutOfBoundsException after 
pressing "reconfigure with XML below".
-              (Fixed in RC2, but wasn't included in release notes.)
-[LOG4J2-666]  AsyncLoggerContextSelector should ensure that different 
AsyncLoggerContext objects created by web app classloaders have unique names.
-[LOG4J2-683]  Fix annotation processor warnings on JDK 1.7+. Thanks to 
Jurriaan Mous.
-[LOG4J2-694]  Fix strange compilation error that popped up in a test class.
-[LOG4J2-692]  Update documentation to specify only Maven 3 is supported.
-[LOG4J2-690]  Log4j Web test dependencies should be in scope "test" in the 
pom. Thanks to Philip Helger.
-[LOG4J2-682]  Special characters (tab and so on) in PatternLayout do not work. 
Thanks to Scott Harrington.
-[LOG4J2-686]  Core's OptionConverter support for \b is broken (affects 
PatternLayout).
-[LOG4J2-687]  Rename org.apache.logging.log4j.core.util.Closer.closeSilent() 
to closeSilently().
-[LOG4J2-688]  Make org.apache.logging.log4j.core.layout.PatternLayout 
immutable.
-[LOG4J2-707]  Some exceptions are not logged when configuration problems are 
detected.
-
-Changes:
-[LOG4J2-685]  Make org.apache.logging.log4j.core.layout.AbstractLayout 
immutable.
-[LOG4J2-689]  Update Jackson to 2.4.1.
-[LOG4J2-709]  Update Apache Commons Logging to 1.2 from 1.1.3.
-
-
-Apache Log4j 2.0 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
-very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
-org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
-
-For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
-patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
-
-http://logging.apache.org/log4j/2.x/
-
-
-
-
-
-
+http://logging.apache.org/log4j/2.x/
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/a83e006b/src/changes/announcement.vm
----------------------------------------------------------------------
diff --git a/src/changes/announcement.vm b/src/changes/announcement.vm
index 0894330..27053fe 100644
--- a/src/changes/announcement.vm
+++ b/src/changes/announcement.vm
@@ -23,12 +23,10 @@ The ${developmentTeam} is pleased to announce the Log4j 
${relVersion} release!
 
 Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
 Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
+many other modern features such as support for Markers, property substitution 
using Lookups, and asynchronous
+Loggers. In addition, Log4j 2 will not lose events while reconfiguring.
 
-This is the fourth GA release which contains several bugfixes and new 
features. There are two
-new Maven artifacts in this release: log4j-jul and log4j-iostreams. Both 
components are API-based
-with optional Core features.
+This is the fifth GA release. It contains several bugfixes and new features.
 
 ## Hack to improve layout: replace all pairs of spaces with a single new-line
 $release.description.replaceAll("  ", "
@@ -133,181 +131,14 @@ o#if($!issue != "") $issue. #end ${action} #if($!dueto 
!= "")Thanks to $dueto. #
 ## End of main loop
 #end
 
-Apache Log4j ${relVersion} requires a minimum of Java 6 to build and run. 
Basic compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
+Apache Log4j ${relVersion} requires a minimum of Java 6 to build and run. 
Future releases may require a minimum
+of Java 7.
+
+Basic compatibility with Log4j 1.x is provided through the log4j-1.2-api 
component, however it does not implement some of the
 very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
 org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
 
 For complete information on ${project.name}, including instructions on how to 
submit bug reports,
 patches, or suggestions for improvement, see the Apache ${project.name} 
website:
 
-${project.url}
-
--------------------------------------------------------------------------------
-
-              Apache Log4j 2.0.2 RELEASE NOTES
-
-The Apache Log4j 2 team is pleased to announce the Log4j 2.0.2 release!
-
-Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
-Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
-
-This is the third GA release which contains several bugfixes from the previous 
release.
-
-Bug fixes and enhancements
-
-Changes in this version include:
-
-
-Fixed Bugs:
-o LOG4J2-773:  Site: log4j-core component pages were still using the old logo.
-o LOG4J2-760:  Documentation improvement: link to dependency tree from 
log4j-core component page,
-        link to log4j-core component page from FAQ page.
-o LOG4J2-679:  Resolved race condition that caused log file rotation to fail 
with error: "Unable to create directory ..."
-o LOG4J2-726:  Prevent application from hanging when PatternLayout 
configuration has opening '{' but no closing '}'.
-o LOG4J2-769:  Startup takes a long time if you have empty packages attribute. 
Thanks to Scott Harrington.
-o LOG4J2-763:  Improved asynchronous loggers and appenders to ensure the 
formatted message does not change even if
-        parameters are modified by the application. (ParameterizedMessage was 
already safe.)
-        Improved documentation. Thanks to Stephen Connolly.
-o LOG4J2-729:  Emit warning message to console if no configuration file found.
-o LOG4J2-765:  Improve warning message when missing log4j-core in the 
classpath.
-o LOG4J2-722:  Clarified in documentation that Commons Logging jar is required 
when using log4j-jcl.
-o LOG4J2-723:  Clarified in documentation that SLF4J API jar is required when 
using log4j-slf4j-impl.
-o LOG4J2-759:  Fixed various minor site/documentation issues, mostly 
versioning related.
-o LOG4J2-756:  Prevent JUnit test from creating unnecessary Log4j2Plugins.dat 
during build. Thanks to Scott Harrington.
-
-Changes:
-o LOG4J2-775:  Update Apache Flume to 1.5.0.1 from 1.5.0.
-o LOG4J2-730:  Allow Log4jContextFactory subclasses to specify a custom 
ContextSelector.
-
-
-Apache Log4j 2.0.2 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
-very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
-org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
-
-For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
-patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
-
-http://logging.apache.org/log4j/2.x/
-
--------------------------------------------------------------------------------
-
-              Apache Log4j 2.0.1 RELEASE NOTES
-
-The Apache Log4j 2 team is pleased to announce the Log4j 2.0.1 release!
-
-Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
-Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
-
-This is the first GA release, after thirteen prior releases over the last 4 
years.
-
-?
-
-Changes in this version include:
-
-New features:
-o LOG4J2-725:  Added WebLoggerContextUtils class to log4j-web for helper 
methods useful for asynchronous servlets.
-o LOG4J2-710:  Added documentation for Custom Levels and Custom Loggers.
-
-Fixed Bugs:
-o LOG4J2-744:  Avoid unnecessary Clock calls when TimestampMessage is logged. 
Thanks to Scott Harrington.
-o LOG4J2-704:  Improved error message if configuration file not found.
-o LOG4J2-750:  Webapp configuration page has incorrect class name. Thanks to 
Mike Calmus.
-o LOG4J2-749:  Retain the default date pattern after fixing the ISO8601 
pattern. Thanks to Scott Harrington.
-o LOG4J2-670:  DatePatternConverter ISO8601_PATTERN now conforms to ISO8601.
-o LOG4J2-741:  Reinstate the package configuration attribute for discovering 
custom plugins.
-o LOG4J2-742:  XInclude not working with relative path. Thanks to Pascal 
Chollet.
-o LOG4J2-740:  Fixed typo in webapp manual regarding sample web.xml file. 
Thanks to Kosta Krauth.
-o LOG4J2-738:  RollingFileManager deadlock if async action thread fails to 
start. Thanks to Timothy Stack.
-o LOG4J2-736:  Fixed log4j-bom so that it won't specify a default scope on any 
third party dependencies.
-o LOG4J2-735:  Fixed log4j-bom so that it won't interfere with spring-bom and 
others.
-o LOG4J2-731:  Updated documentation regarding extensions to 
LoggerContextFactory and Log4j 2 providers.
-o LOG4J2-373:  Fixed ClassLoader issues in loading Log4j providers in an OSGi 
environment.
-o LOG4J2-719:  Correctly handle NetworkOnMainThreadException thrown on Android 
during Log4j2 initialization.
-o LOG4J2-716:  Automatically disable log4j JMX when detecting we are running 
on Android.
-o LOG4J2-657:  Fixed AbstractDatabaseManager to close connection on 
writeInternal error. Thanks to Stefan Wehner.
-o LOG4J2-713:  Android: java.lang.VerifyError: 
org/apache/logging/log4j/core/util/Closer Thanks to Nelson Melina.
-o LOG4J2-703:  Android: Could not find class 'javax.naming.InitialContext', 
referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup. 
Thanks to Nelson Melina.
-
-
-
-Apache Log4j 2.0.1 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
-very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
-org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
-
-For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
-patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
-
-http://logging.apache.org/log4j/2.x/
-
--------------------------------------------------------------------------------
-
-              Apache Log4j 2.0 RELEASE NOTES
-
-The Apache Log4j 2 team is pleased to announce the Log4j 2.0 release!
-
-Apache log4j is a well known framework for logging application behavior. Log4j 
2 is an upgrade to
-Log4j that provides significant improvements over its predecessor, Log4j 1.x, 
and provides
-many of the improvements available in Logback while fixing some inherent 
problems in Logback's
-architecture.
-
-This is the first GA release, after thirteen prior releases over the last 4 
years.
-
-GA Release
-
-Changes in this version include:
-
-New features:
-o LOG4J2-519:  Added support for generating custom logger wrappers that 
replace the existing log levels
-        and extended logger wrappers that add custom log levels to the 
existing ones.
-o LOG4J2-696:  RegexFilter does not match multiline log messages.
-
-Fixed Bugs:
-o LOG4J2-705:  Fixed issue where Async Logger does not log thread context 
stack data.
-        API change: added method getImmutableStackOrNull() to 
ThreadContext.ContextStack interface.
-o LOG4J2-631:  Update docs to clarify how to use formatter logger and standard 
logger together.
-o LOG4J2-441:  LoggerConfigs with no Level now inherit the Level from their 
parent.
-o LOG4J2-703:  Android: Could not find class 'javax.naming.InitialContext', 
referenced from method org.apache.logging.log4j.core.lookup.JndiLookup.lookup. 
Thanks to Nelson Melina.
-o LOG4J2-699:  PatternLayout manual page missing documentation on 
header/footer.
-o LOG4J2-625:  Fixed Serialization error with SocketAppender and Async Loggers.
-        (Fixed in RC2, but wasn't included in release notes.)
-o LOG4J2-538:  JMX GUI: fixed occasional ArrayIndexOutOfBoundsException after 
pressing "reconfigure with XML below".
-        (Fixed in RC2, but wasn't included in release notes.)
-o LOG4J2-666:  AsyncLoggerContextSelector should ensure that different 
AsyncLoggerContext objects created by web app classloaders have unique names.
-o LOG4J2-683:  Fix annotation processor warnings on JDK 1.7+. Thanks to 
Jurriaan Mous.
-o LOG4J2-694:  Fix strange compilation error that popped up in a test class.
-o LOG4J2-692:  Update documentation to specify only Maven 3 is supported.
-o LOG4J2-690:  Log4j Web test dependencies should be in scope "test" in the 
pom. Thanks to Philip Helger.
-o LOG4J2-682:  Special characters (tab and so on) in PatternLayout do not 
work. Thanks to Scott Harrington.
-o LOG4J2-686:  Core's OptionConverter support for \b is broken (affects 
PatternLayout).
-o LOG4J2-687:  Rename org.apache.logging.log4j.core.util.Closer.closeSilent() 
to closeSilently().
-o LOG4J2-688:  Make org.apache.logging.log4j.core.layout.PatternLayout 
immutable.
-o LOG4J2-707:  Some exceptions are not logged when configuration problems are 
detected.
-
-Changes:
-o LOG4J2-685:  Make org.apache.logging.log4j.core.layout.AbstractLayout 
immutable.
-o LOG4J2-689:  Update Jackson to 2.4.1.
-o LOG4J2-709:  Update Apache Commons Logging to 1.2 from 1.1.3.
-
-
-Apache Log4j 2.0 requires a minimum of Java 6 to build and run. Basic 
compatibility with
-Log4j 1.x is provided through the log4j-1.2-api component, however it does not 
implement some of the
-very implementation specific classes and methods. The package names and Maven 
groupId have been changed to
-org.apache.logging.log4j to avoid any conflicts with log4j 1.x.
-
-For complete information on Apache Log4j 2, including instructions on how to 
submit bug reports,
-patches, or suggestions for improvement, see the Apache Apache Log4j 2 website:
-
-http://logging.apache.org/log4j/2.x/
-
-
-
-
-
-
+${project.url}
\ No newline at end of file

http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/a83e006b/src/changes/changes.xml
----------------------------------------------------------------------
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 2bd8b73..9a765da 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -23,7 +23,7 @@
     <title>Changes</title>
   </properties>
   <body>
-    <release version="2.2" date="2015-??-??" description="GA Release 2.2">
+    <release version="2.2" date="2015-02-22" description="GA Release 2.2">
       <action issue="LOG4J2-938" dev="rpopma" type="fix" due-to="Mauro 
Molinari">
         (JMX) To avoid memory leaks when web applications are restarted, JMX 
notifications are sent from
         the caller thread in web applications. For non-web applications 
notifications are sent from a background thread
@@ -124,7 +124,7 @@
       <action issue="LOG4J2-900" dev="ggregory" type="update">
         Update Apache Flume from 1.5.0.1 to 1.5.2.
       </action>
-    </release>      
+    </release>
     <release version="2.1" date="2014-10-19" description="GA Release 2.1">
       <action issue="LOG4J2-676" dev="rgoers" type="fix" due-to="Stefan 
Bodewig">
         Some typo fixes and enhancements for the site.

Reply via email to