Ralph Goers | 10 Jun 07:41 2016

[ANNOUNCEMENT] Log4j 2.6.1 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.6.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 other modern features such as support for Markers, property substitution using Lookups, multiple patterns on
a PatternLayout and asynchronous Loggers. In addition, Log4j 2 will not lose events while reconfiguring.

This is the eleventh GA release. It is primarily a bugfix release. More details on the fixes are itemized below.

Note that subsequent to the 2.6 release a minor source incompatibility was found due to the addition of new methods to
the Logger interface. If you have code that does:

logger.error(null, “This is the log message”, throwable);

or similar with any log level you will get a compiler error saying the reference is ambiguous. To correct this either do:

logger.error(“This is the log message”, throwable);

or

logger.error((Marker) null, “This is the log message”, throwable);

Log4j 2.6 maintains binary compatibility with previous releases.

GA Release 2.6.1

Changes in this version include:

New features:
o LOG4J2-1411: Add documentation about plugin builders compared to factories.

Fixed Bugs:
o LOG4J2-1405: OnStartupTriggeringPolicy was forcing a rollover of empty files at startup and would append a
second footer that was added by the prior shutdown.
o LOG4J2-1406: Fixed bug in ReusableParameterizedMessage where Throwable was never updated so first error was logged over
and over again and subsequent errors were not logged. Thanks to Trask Stalnaker.
o LOG4J2-1409: Fixed ArrayIndexOutOfBoundsException that may occur in ReusableParameterizedMessage. Thanks to Shahan.
o LOG4J2-997: Add filter and remove filter were not working properly in AbstractFilterable. Thanks to Maytee Chinavanichkit.
o LOG4J2-1032: Change RenameAction to use java.nio to better report rename failures.
o LOG4J2-1407: Misleading WARN log events from Log4j about message factories and unexpected formatting. Thanks to Gary Gregory.
o LOG4J2-1408: The module log4j-liquibase is missing from BOM POM. Thanks to Gary Gregory.
o LOG4J2-1180: Logger cache does not account for message factory. Thanks to Gary Gregory.
o LOG4J2-1402: Fix regression in properties configuration to support arbitrary component ids.

Changes:
o LOG4J2-1385: (GC) CSV layouts should not create a new CSVPrinter for each log event. Requires Apache Commons CSV 1.4.
o LOG4J2-1398: Update liquibase-core from 3.4.2 to 3.5.1.
o LOG4J2-1399: Update Apache Commons CSV from 1.3 to 1.4.


Apache Log4j 2.6.1 requires a minimum of Java 7 to build and run. Log4j 2.3 was the last release that
supported Java 6.

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/
Ralph Goers | 29 May 23:20 2016

[ANNOUNCEMENT] Log4j 2.6 released


              Apache Log4j 2.6 RELEASE NOTES

The Apache Log4j 2 team is pleased to announce the Log4j 2.6 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 other modern features such as support for Markers, property substitution using Lookups, multiple
patterns on
a PatternLayout and asynchronous Loggers. In addition, Log4j 2 will not lose events while reconfiguring.

This is the tenth GA release. It contains several bugfixes and new features. The new features include
the ability to be "garbage-free" (avoid allocating temporary objects) while logging if certain
conditions are met,
a new YAML Layout, the ability to merge configuration files, and documenting Log4j's performance against
other logging
frameworks and in various logging configurations. More details on the features and bugfixes are itemized below.

Note that subsequent to the release a minor source incompatibility was found due to the addition of new
methods to
the Logger interface. If you have code that does:

logger.error(null, “This is the log message”, throwable);

or similar with any log level you will get a compiler error saying the reference is ambiguous.  To correct
this either do:

logger.error(“This is the log message”, throwable);

or 

logger.error((Marker) null, “This is the log message”, throwable);

Log4j 2.6 maintains binary compatibility with previous releases.

GA Release 2.6

Changes in this version include:

New features:
o LOG4J2-1270:  (GC) Added support for garbage-free logging in steady state.
        This includes Async Loggers and logging synchronously to the console and to a file,
        but does not include the AsyncAppender. This release makes the GelfLayout and
        the main patterns in the PatternLayout garbage-free. 
o LOG4J2-1297:  (GC) Added manual page on garbage-free logging. 
o LOG4J2-1373:  (GC) Update Logger wrapper Generator tool to generate methods for the new Logger methods. 
o LOG4J2-1326:  (GC) Added methods to the Logger interface for logging CharSequence messages. 
o LOG4J2-1344:  (GC) FileAppender, RollingFileAppender and MemoryMappedFileAppender are now also
garbage-free by default. 
o LOG4J2-1278:  (GC) Added unrolled varargs methods to Logger API, added Unbox utility to avoid
auto-boxing when logging primitive values. 
o LOG4J2-1271:  (GC) Add MessageFactory that avoid allocation by reusing a cached ParameterizedMessage
instance. 
o LOG4J2-1293:  (GC) Add interface StringBuilderFormattable to enable converting Messages and
parameters to text without allocating temporary objects.
        ParameterizedMessage, ObjectMessage, SimpleMessage and ThreadDumpMessage now implement
StringBuilderFormattable. 
o LOG4J2-1274:  (GC) Add encode(LogEvent, ByteBufferDestination) method to Layout API to enable
converting LogEvents to bytes without creating temporary objects. 
o LOG4J2-1362:  Added a YAML layout. Thanks to Gary Gregory. 
o LOG4J2-1179:  Documented benchmark results comparing Log4j 2 performance to other logging libraries. 
o LOG4J2-1011:  Document dependencies for layouts. 
o LOG4J2-621:  Pattern to drop first N package parts. Thanks to Lee Theobald, Kamal Mettananda, Gary
Gregory. 
o LOG4J2-494:  Support merging configurations to for a composite configuration. Thanks to Philipp
Knobel. 
o LOG4J2-1357:  Option to not log stack traces for logged Throwables in GelfLayout. 
o LOG4J2-1348:  Add an AutoCloseable ThreadContext class: CloseableThreadContext. Thanks to Greg
Thomas, Gary Gregory. 
o LOG4J2-1299:  Add pattern converter for thread id and priority in PatternLayout. 
o LOG4J2-124:  Add shutdown methods to LogManager. 
o LOG4J2-1221:  Added async logger Timeout wait strategy and made this the default wait strategy for async loggers.
        This prevents a rare deadlock that may occur on Solaris. Thanks to Michael Barker. 
o LOG4J2-1080:  Added option to discard events below a certain log level if the async logger ring buffer
        or async appender queue is full. 
o LOG4J2-1237:  Make PatternLayout header and footer accept a pattern. Thanks to Mike Calmus, Gary
Gregory. 
o LOG4J2-1244:  Make header and footer values customizable in JSONLayout. Thanks to Anshu Garg, Remko
Popma, Gary Gregory. 
o LOG4J2-1245:  Make CSV Layout header and footers accept patterns. 
o LOG4J2-1192:  Dynamic Subject for SMTP Appender. Thanks to Jörg Bretschneider, Gary Gregory. 
o LOG4J2-1277:  FormattedMessage, MessageFormatMessage and StringFormattedMessage should support
passing in a Locale to ensure appropriate formatting. Thanks to Gary Gregory, Ludovic Hochet. 
o LOG4J2-1303:  Add documentation links to runtime dependencies in each component intro page. 
o LOG4J2-1252:  JeroMqAppender should support layouts. 
o LOG4J2-1217:  PatternLayout option to limit length of text. Thanks to Thies Wellpott. 
o LOG4J2-1133:  Add JNDI lookup documentation. 
o LOG4J2-1169:  PatternLayout: Possible variable substitution in equals substitution parameter.
Thanks to Gerald Kritzinger. 

Fixed Bugs:
o LOG4J2-1281:  (GC) LoggerConfig.getProperties() should not allocate on each call. 
o LOG4J2-1269:  (GC) AsyncLogger should use thread-local translator by default. 
o LOG4J2-623:  Generate MDC properties as a JSON map in JSONLayout, with option to output as list of map
entries. 
o LOG4J2-1387:  Fixed memory leak related to shutdown hook. 
o LOG4J2-1382:  Copying a MutableLogEvent using Log4jLogEvent.Builder should not unnecessarily obtain
caller location information. 
o LOG4J2-1372:  XMLLayout indents, but not the first child tag (Event). Thanks to Kamal Mettananda, Gary
Gregory. 
o LOG4J2-1363:  Properties Configuration did not support includeLocation attribute on Loggers. 
o LOG4J2-1263:  The ConfigurationSource was not saved for BuiltConfigurations so monitor interval had no
effect. 
o LOG4J2-1369:  "xz" compression results in plaintext, uncompressed files. Thanks to Alex Birch, Gary
Gregory. 
o LOG4J2-1368:  (Log4j-internal) StatusLogger dropped exceptions when logging parameterized
messages. 
o LOG4J2-1336:  LoggerFactory in 1.2 API module is not compatible with 1.2. Thanks to Zbynek Vyskovsky. 
o LOG4J2-1354:  No configuration reload is triggered under Windows when replacing the configuration file
with one that has older last modified date. Thanks to Arkadiusz Adolph. 
o LOG4J2-1346:  Exception from Log4jServletContextListener prevents jetty-maven-plugin run-forked. 
o LOG4J2-1339:  (Perf) AsyncLogger performance optimization: avoid calling instanceof
TimestampMessage in hot path. 
o LOG4J2-1324:  Improve error handling in the Async Logger background thread: the new default exception
handler no longer rethrows the error. 
o LOG4J2-1309:  Configuration file error does not show cause exception. 
o LOG4J2-1289:  Change flow logging text from "entry' to "Enter" and "exit" to "Exit". 
o LOG4J2-1284:  Made default MessageFactory configurable. 
o LOG4J2-1280:  Deprecate org.apache.logging.log4j.util.MessageSupplier. 
o LOG4J2-1280:  Logger methods taking Supplier parameters now correctly handle cases where the supplied
value is a Message. 
o LOG4J2-1268:  FixedDateFormat was incorrect for formats having MMM with the French locale. 
o LOG4J2-1222:  Creation of a LoggerContext will fail if shutdown is in progress. LogManager will default
to SimpleLogger instead. 
o LOG4J2-1260:  TlsSyslogFrame calculates message length incorrectly. Thanks to Blake Day, Gary
Gregory. 
o LOG4J2-1258:  Async DynamicThresholdFilter does not use the log event's context map. Thanks to Francis
Lalonde. 
o LOG4J2-1232:  Incorrect log rotation in last week of year. Thanks to Nikolai. 
o LOG4J2-1248:  Fixed broken nanotime in pattern layout. 
o LOG4J2-908:  JSONLayout doesn't add a comma between log events. Thanks to Konstantinos Liakos, Patrick
Flaherty, Robin Coe, Gary Gregory. 
o LOG4J2-1230:  Don't concatenate SYSLOG Messages. Thanks to Vladimir Hudec, Ralph Goers, Gary Gregory. 
o LOG4J2-1238:  org.apache.logging.log4j.core.net.TcpSocketManager and other classes does not
report internal exceptions to the status logger. 
o LOG4J2-1212:  Fix documentation to specify the correct default wait strategy used by async loggers. 
o LOG4J2-1215:  Documentation/XSD inconsistencies. Thanks to Erik Kemperman. 
o LOG4J2-1276:  LoggerMessageSupplierTest and LoggerSupplierTest are Locale sensitive. Thanks to
Ludovic Hochet. 
o LOG4J2-1251:  Fix JUL bridge issue where LogRecord.getParameters() is used when null. Thanks to Romain
Manni-Bucau. 
o LOG4J2-1254:  Fix typo in Flow Tracing documentation. Thanks to Josh Trow. 
o LOG4J2-920:  ClassNotFoundException for BundleContextSelector when initialising in an OSGi
environment. Thanks to Ludovic Hochet. 
o LOG4J2-1275:  Fix RollingAppenderNoUnconditionalDeleteTest repeat test runs from failing. Thanks to
Ludovic Hochet. 
o LOG4J2-1262:  Stop throwing unnecessary exception in
Log4jServletContextListener.contextDestroyed(). 
o LOG4J2-1227:  NullPointerException in MapLookup.lookup if the event is null. Thanks to Olivier
Lemasle. 
o LOG4J2-1050:  Add a Log4jLookup class to help write log files relative to log4j2.xml. Thanks to Adam
Retter. 
o LOG4J2-1310:  JndiLookup mindlessly casts to String and should use String.valueOf(). 
o LOG4J2-248:  Log4jWebInitializerImpl: Use Thread instead of Class for fallback classloader. 
o LOG4J2-1330:  Fix NoClassDefFoundError in ReflectionUtil on Google App Engine. 

Changes:
o LOG4J2-1356:  (GC) GelfLayout does now support garabage-free logging (with compressionType=OFF). 
o LOG4J2-1343:  (GC) ConsoleAppender is now garbage-free by default. This logic is reusable for all
AbstractOutputStreamAppender subclasses. 
o LOG4J2-1318:  (GC) Avoid allocating unnecessary temporary objects in LoggerContext's getLogger
methods. 
o LOG4J2-1333:  (GC) Avoid allocating unnecessary temporary objects in MarkerManager's getMarker
methods. 
o LOG4J2-1321:  (GC) Avoid allocating unnecessary temporary objects in PatternLayout's
NamePatternConverter and ClassNamePatternConverter. 
o LOG4J2-1271:  (GC) ParameterizedMessage optimizations to avoid or at least postpone allocating
temporary objects. 
o LOG4J2-1283:  (GC) Provide ThreadLocal-based gc-free caching mechanism in DatePatternConverter for
non-webapps. 
o LOG4J2-1291:  (GC) Update PatternLayout to utilize gc-free mechanism for LogEvent processing. 
o LOG4J2-1292:  (GC) Update RandomAccessFileAppender and RollingRandomAccessFileAppender to utilize
gc-free Layout.encode() method. 
o LOG4J2-1272:  (GC) Improve LoggerConfig's data structure for AppenderControl objects to avoid
allocating temporary objects during
        traversal for each log event. 
o LOG4J2-1375:  Update SLF4J from 1.7.13 to 1.7.21. 
o LOG4J2-1374:  Migrate tests from Logback 1.1.3 to 1.1.7. 
o LOG4J2-1384:  Update Apache Commons CSV from 1.2 to 1.3. 
o LOG4J2-1365:  (Log4j-internal) Provide message text as CharSequence for some message types to optimize
some layouts. 
o LOG4J2-1345:  (Doc) Clarify documentation for properties that control Log4j behaviour. 
o LOG4J2-1255:  Add enhanced entry and exit methods. 
o LOG4J2-1380:  Update Jackson from 2.7.3 to 2.7.4. 
o LOG4J2-1304:  Update Jackson from 2.7.0 to 2.7.2. 
o LOG4J2-1253:  Update LMAX Disruptor from 3.3.2 to 3.3.4. 
o LOG4J2-1219:  Update SLF4J from 1.7.12 to 1.7.13. 
o LOG4J2-1239:  Update Jackson from 2.6.3 to 2.6.4. 
o LOG4J2-1249:  Update Jackson from 2.6.4 to 2.7.0. 
o LOG4J2-1351:  Update Jackson from 2.7.2 to 2.7.3. 
o LOG4J2-1240:  Update Liquibase from 3.3.5 to 3.4.2. 
o LOG4J2-1294:  Update Kafka client from 0.9.0.0 to 0.9.0.1. 
o LOG4J2-1352:  Update javax.mail from 1.5.4 to 1.5.5. 
o LOG4J2-1358:  Update Apache Commons Compress from 1.10 to 1.11. 
o LOG4J2-1388:  Update Google java-allocation-instrumenter from 3.0 to 3.0.1. 
o LOG4J2-1233:  Misleading Value In Properties Example. Thanks to Bahri Gencsoy. 
o LOG4J2-1300:  Remove serializability from classes that don't need it. 
o LOG4J2-1306:  JeroMqAppender should use ShutdownCallbackRegistry instead of runtime hooks. 
o LOG4J2-1308:  Remove need to pre-specify appender et al. identifiers in property file config format. 
o LOG4J2-1206:  org.apache.logging.log4j.core.LoggerContext#updateLoggers should call
firePropertyChangeEvent. 
o LOG4J2-1322:  Update Log4j 1.x migration guide to include information about system property lookup
syntax changes. 

Apache Log4j 2.6 requires a minimum of Java 7 to build and run. Log4j 2.3 was the last release that
supported Java 6.

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 Wiki | 26 May 05:04 2016
Picon

[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Logging Wiki" for change notification.

The "Log4j2ReleaseGuide" page has been changed by RalphGoers:
https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=38&rev2=39

   1. Login to http://repository.apache.org using your ASF credentials. Select "Staging Repositories"
then check the {{{org.apache.logging}}} repository and close it.
   1. Check out the release tag that was created via the Maven release plugin using {{{git checkout tags/tagname}}}.
   1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
-  1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}} and copy to your account at
{{{people.apache.org}}} with {{{scp log4j.zip
myUsername <at> people.apache.org:/home/myUsername}}}. Unzip the contents into your public html directory.
+  1. Zip the contents of {{{$HOME/log4j}}} with {{{zip -r log4j.zip log4j}}}. Commit the site to your
github.io account. 
   1. Generate the release vote email:
      a. Create the email addressed to log4j-dev <at> logging.apache.org and private <at> logging.apache.org.
Sending the email to the PMC is not strictly necessary, but due to the small size of the logging PMC it is
expedient to do so in order to get the required votes.
      a. Copy the changes in the release from {{{RELEASE-NOTES.txt}}} into the email.

Ralph Goers | 11 Dec 01:51 2015

[ANNOUNCEMENT] Apache Log4j 2.5 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.5 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 other modern features such as support for Markers, property substitution using Lookups, multiple patterns on

a PatternLayout and asynchronous Loggers. In addition, Log4j 2 will not lose events while reconfiguring.


This is the ninth GA release. It contains several bugfixes and new features. The new features include

the ability to specify delete actions during file rollover, a CRON-based triggering policy for file rollover,

Support for JSR 223 scripts in filters, pattern selectors and delete actions, and a policy for removing

idle appenders from the RoutingAppender. More details on the features and bugfixes are itemized below.


Log4j 2 requires a minimum of Java 7.


GA Release 2.5


Changes in this version include:


New features:

o LOG4J2-435:  Added support for custom delete actions triggered by a rollover. Thanks to Robert Schaft.

o LOG4J2-89:  Allow rollover to occur at any time. Add CronTriggeringPolicy.

o LOG4J2-1136:  Add support for JSR 223 scripts in filters and the PatternSelector.

o LOG4J2-1168:  Add getters for source and destination file in file rename action. Thanks to Steven Swor.

o LOG4J2-1175:  Add getters for classes in org.apache.logging.log4j.core.appender.rolling.action.

o LOG4J2-898:  Added system property to allow users to control whether messages should be formatted in the background.

o LOG4J2-1178:  Support use-case for JDBC's CommonDataSource.setLogWriter(PrintWriter) and java.sql.DriverManager.setLogWriter(PrintWriter).

o LOG4J2-1187:  Support use case for java.sql.DriverManager.setLogStream(PrintStream).


Fixed Bugs:

o LOG4J2-324:  Reduced memory usage of status messages in bounded queue; support zero-length queue that stores no messages.

o LOG4J2-1173:  Fixed rollover error when copying to a directory mapped to a remote Linux host.

o LOG4J2-1195:  Make KafkaAppender support SerializedLayout. Thanks to Melvin Du.

o LOG4J2-381:  Allow triggering policy and rollover strategy to be modified during reconfiguration. Thanks to Anthony Baldocchi.

o LOG4J2-1029:  Performance improvement when gathering location information. Thanks to Stefan Leonhartsberger.

o LOG4J2-1172:  Fixed ThreadLocal leak [AsyncLogger$Info] on Tomcat when using AsyncLoggerContextSelector.

o LOG4J2-1176:  Fixed memory leak when log4j jars are in Tomcat's lib folder.

o LOG4J2-1180:  Logger cache does not account for message factory. Thanks to Mikael Ståldal.

o LOG4J2-879:  Documentation: fixed minor issues with the site and manual pages.

o LOG4J2-999:  RollingFileAppender should also roll over when log event time is equal to rollover time, not only when later. Thanks to Joan Balagueró.

o LOG4J2-873:  Fixed bug where omitting the <display-name> element in web.xml caused incorrect log4j initialization,

        resulting in memory leaks when the web application was stopped or reloaded. Thanks to Martin Dickins, LC, Luke Woodward.

o LOG4J2-323:  Better web app support for async loggers: Fixed a memory leak that occurred when the logging jars are placed

        in the container's classpath and the configuration file uses AsyncRoot/AsyncLogger.

        The problem was that the first web application started the Disruptor background thread [AsyncLoggerConfig-1] but did not stop it until all web apps are stopped.

        Each web application now has its own Disruptor which is stopped/started together with the web app.

o LOG4J2-493:  Better web app support for async loggers: it is now possible to place the logging jars in the container's

        classpath when making all loggers asynchronous by using AsyncLoggerContextSelector. This fixes a problem where

        logging would stop working after stopping and restarting a web application.

o LOG4J2-1171:  Use servlet context name for logger context name when available.

o LOG4J2-1159:  Fixed a ThreadLocal memory leak in Tomcat8 that mentions AsyncLoggers when Async Loggers are not used.

o LOG4J2-1166:  AbstractConfiguration executor should use a DaemonThreadFactory.

o LOG4J2-1165:  Improve Log4j initialization status messages.

o LOG4J2-1156:  Web site corrections and updates.

o LOG4J2-1158:  Log4J JUL adapter is using MessageFormat on String passed by java.util.function.Supplier<String>. Thanks to Michael Fortin, Gary Gregory.

o LOG4J2-801:  org.apache.logging.log4j.core.Logger should be serializable.

o LOG4J2-1157:  Fix compilation error for classes annotated with <at> Plugin. Thanks to Norbert Bartels.

o LOG4J2-948:  Fix plugin documentation error about Converters. Thanks to Andrew Flower.

o LOG4J2-1193:  Prefix all thread names Log4j creates with "Log4j2-".

o LOG4J2-1194:  Documentation does not match parameters for LoggerNameLevelRewritePolicy. Thanks to Adam Brin.

o LOG4J2-1196:  MongoDbConnection does not close MongoClient. Thanks to René Zanner.


Changes:

o LOG4J2-649:  Add PurgePolicy and IdlePurgePolicy to RoutingAppender. Thanks to Aleksey Zvolinsky.

o LOG4J2-1202:  Remove ConfigurationMonitor. The WatchManager is now used to check for configuration changes.

o LOG4J2-1174:  Update Jackson from 2.6.2 to 2.6.3.

o LOG4J2-1207:  Update kafka-clients from 0.8.2.2 to 0.9.0.0.



Apache Log4j 2.5 requires a minimum of Java 7 to build and run. Log4j 2.3 was the last release that

supported Java 6.


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/


Stefan Bodewig | 10 Dec 06:30 2015
Picon
Gravatar

[ANN] Apache log4net 1.2.15 Released


The Apache log4net team is pleased to announce the release of Apache
log4net 1.2.15.  The release is available for download at

        http://logging.apache.org/log4net/download_log4net.cgi

The Apache log4net library is a tool to help the programmer output log
statements to a variety of output targets.  log4net is a port of the
excellent Apache log4j framework to the Microsoft(R) .NET runtime.

This is the last log4net release that provides assemblies for .NET 1.x
or 2.0 and Mono 1.x.  We intend to stay compatible with those
frameworks in future releases but people using said frameworks will
need to build the binaries from the source distribution themselves.

People using said frameworks should notice that they will eventually
have to maintain compatibility in the rare case that future
modifications to log4net broke the compatibility. Patches are always
welcome! We decided to take this step because supporting these old
frameworks consumes a large amount of resources while the effort is
probably wasted.

See the release-notes at

    http://logging.apache.org/log4net/release/release-notes.html

for a full list of changes.

Please verify signatures using the KEYS file available at the above
location when downloading the release.

For complete information on log4net, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the
Apache log4net website:

        http://logging.apache.org/log4net/

Apache Wiki | 7 Dec 00:54 2015
Picon

[Logging Wiki] Update of "Log4j2ReleaseGuide" by RalphGoers

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Logging Wiki" for change notification.

The "Log4j2ReleaseGuide" page has been changed by RalphGoers:
https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=37&rev2=38

   1. Run {{{mvn -P release-notes generate-resources}}} to create the release notes.
   1. Update {{{src/changes/changes.xml}}} with the release date.
   1. Run {{{git add, git commit, and git push}}} to commit the {{{RELEASE-NOTES.txt}}} file that was just generated.
-  1. Run {{{mvn -P apache-release release:prepare release:perform -DreleaseVersion=n.n
-DdevelopmentVersion=n.n-SNAPSHOT}}} to start the release. Enter the password to your signing key
when prompted.
+  1. Run {{{mvn -P apache-release release:prepare release:perform -DreleaseVersion=n.n
-DdevelopmentVersion=n.n-SNAPSHOT -Dtag=log4j-n.n-rcn}}} to start the release. Enter the password
to your signing key when prompted.
   1. Login to http://repository.apache.org using your ASF credentials. Select "Staging Repositories"
then check the {{{org.apache.logging}}} repository and close it.
   1. Check out the release tag that was created via the Maven release plugin using {{{git checkout tags/tagname}}}.
   1. Run {{{mvn site}}} in the tag directory. When that completes run {{{mvn site:stage
-DstagingDirectory=$HOME/log4j}}} where {{{$HOME}}} is your home directory.
 <at>  <at>  -64, +64  <at>  <at> 

      a. Provide the command to download all the artifacts: {{{wget -e robots=off --cut-dirs=3 -r -p -np
--no-check-certificate $LINK}}} where {{{$LINK}}} is the URL to the repository you just closed (plus
the {{{org/apache/logging/log4j/}}} path appended).
      a. Provide a list of the artifacts by copying from the email notification sent from the Nexus
Repository.<<FootNote(Nexus has not been sending this email for the past few releases at least)>>
   1. If the release vote fails proceed as described in the section below, otherwise if it passes:
+     a. Create a new tag named log4j-n.n from the log4j-n.n-rcn tag.
      a. Download all the distribution files from the Nexus repository (you can download using the wget above and
then going to the distribution sub-directory).
      a. Rename the distribution files back to their original names (Maven renamed them when they were deployed
to Nexus) using {{{for f in log4j-distribution-*; do mv $f $(echo $f | sed
's/^log4j-distribution-/apache-log4j-/g'); done}}}
      a. Delete the {{{*.asc.md5}}} and {{{*.asc.sha1}}} files and {{{*.pom*}}}.

Stefan Bodewig | 6 Dec 06:29 2015
Picon
Gravatar

[VOTE] Release log4net 1.2.15 Based on RC1


Hi

with 1.2.14 we've introduced a serious regression inside the ADO.NET
appender - also we seem to have missed a few crucial patches needed to
make async/await supported properly.  Therefore a new release is
warranted.

log4net 1.2.15 RC1 is available for review here:
  https://dist.apache.org/repos/dist/dev/logging/log4net
    (revision 11436)

Details of changes since 1.2.15 are in the release notes:
  http://home.apache.org/~bodewig/log4net-1.2.15/site/release/release-notes.html

I have tested this with Mono and several .NET frameworks using NAnt.

The tag is here:
  https://svn.apache.org/repos/asf/logging/log4net/tags/1.2.15RC1
    (revision 1717718)

Site:
  http://home.apache.org/~bodewig/log4net-1.2.15/

RAT Report:
  http://home.apache.org/~bodewig/log4net-1.2.15/rat-report.html

Votes, please.  This vote will close in 72 hours, 0530 GMT 9-Dec 2015

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...

Thanks! 
Roman Shaposhnik | 1 Dec 07:30 2015
Picon
Gravatar

FOSDEM 2016 - take action by 4th of December 2015

As most of you probably know FOSDEM 2016 (the biggest,
100% free open source developer conference) is right 
around the corner:
   https://fosdem.org/2016/

We hope to have an ASF booth and we would love to see as
many ASF projects as possible present at various tracks
(AKA Developer rooms):
   https://fosdem.org/2016/schedule/#devrooms

This year, for the first time, we are running a dedicated
Big Data and HPC Developer Room and given how much of that
open source development is done at ASF it would be great
to have folks submit talks to:
   https://hpc-bigdata-fosdem16.github.io

While the CFPs for different Developer Rooms follow slightly 
different schedules, but if you submit by the end of this week 
you should be fine.

Finally if you don't want to fish for CFP submission URL,
here it is:
   https://fosdem.org/submit

If you have any questions -- please email me *directly* and
hope to see as many of you as possible in two months! 

Thanks,
Roman.

Rich Bowen | 25 Nov 18:32 2015
Gravatar

[ANNOUNCE] CFP open for ApacheCon North America 2016

Community growth starts by talking with those interested in your
project. ApacheCon North America is coming, are you?

We are delighted to announce that the Call For Presentations (CFP) is
now open for ApacheCon North America. You can submit your proposed
sessions at
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp
for big data talks and
http://events.linuxfoundation.org/events/apachecon-north-america/program/cfp
for all other topics.

ApacheCon North America will be held in Vancouver, Canada, May 9-13th
2016. ApacheCon has been running every year since 2000, and is the place
to build your project communities.

While we will consider individual talks we prefer to see related
sessions that are likely to draw users and community members. When
submitting your talk work with your project community and with related
communities to come up with a full program that will walk attendees
through the basics and on into mastery of your project in example use
cases. Content that introduces what's new in your latest release is also
of particular interest, especially when it builds upon existing well
know application models. The goal should be to showcase your project in
ways that will attract participants and encourage engagement in your
community, Please remember to involve your whole project community (user
and dev lists) when building content. This is your chance to create a
project specific event within the broader ApacheCon conference.

Content at ApacheCon North America will be cross-promoted as
mini-conferences, such as ApacheCon Big Data, and ApacheCon Mobile, so
be sure to indicate which larger category your proposed sessions fit into.

Finally, please plan to attend ApacheCon, even if you're not proposing a
talk. The biggest value of the event is community building, and we count
on you to make it a place where your project community is likely to
congregate, not just for the technical content in sessions, but for
hackathons, project summits, and good old fashioned face-to-face networking.

--

-- 
rbowen <at> apache.org
http://apache.org/

Christian Grobmeier | 20 Nov 16:33 2015
Picon
Gravatar

[ANNOUNCEMENT] Welcome Ralph Goers as the new Apache Logging Chair

Hello all,

I was the chair of the Apache Logging Services project for 3 1/2 years.
Thank you, it was a great time. But it is time to move on. I think it is
critical for ASF projects to let the Chair role rotate. 

At Logging Services, we agreed to discuss the role each year at the time
of the ASF members meeting. We did that. We will continue to do that (at
least that's my hope! :)).

The PMC discussed who could fill the role of the Logging Chair, and
while we have many great people among us, we unanimously voted for Ralph
Goers.

Ralph wrote the first versions of what became Log4j 2.0. He wrote large
parts of it until a fantastic community grew around the project. Without
him and his hard work, we would still be stuck on Log4j 1.x times when
things didn't look so bright. 
Ralph is not only an experienced developer but also a great teammate and
knows the Apache way in and out. 

Now I am very happy to say he accepted our vote, and the ASF Board
confirmed him in his role, effective immediately.

Welcome, Ralph! All the best for your new role, and may the force be
with you!

Cheers,
Christian

PS: if you are confused by the terms PMC, Chair or whatever, I'd like to
invite you to read the blog I posted when I became chair:
http://www.grobmeier.de/hey-i-became-a-vice-president-07072012.html

Or the official docs:
http://www.apache.org/foundation/how-it-works.html

Stefan Bodewig | 11 Nov 13:12 2015
Picon
Gravatar

[ANN] Apache log4net 1.2.14 Released


The Apache log4net team is pleased to announce the release of Apache
log4net 1.2.14.  The release is available for download at

        http://logging.apache.org/log4net/download.html

The Apache log4net library is a tool to help the programmer output log
statements to a variety of output targets.  log4net is a port of the
excellent Apache log4j framework to the Microsoft(R) .NET runtime.

The log4net 1.2.14 release fixes a problem with logical thread
properties used together with async/await as well as a bugs.  It also
adds a new option to SmtpPickupDirAppender.

See the release-notes at

    http://logging.apache.org/log4net/release/release-notes.html

for a full list of changes.

Please verify signatures using the KEYS file available at the above
location when downloading the release.

For complete information on log4net, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the
Apache log4net website:

Gmane