Apache Wiki | 31 Aug 10:58 2014
Picon

[Logging Wiki] Update of "AdminGroup" by ChristianGrobmeier

Dear Wiki user,

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

The "AdminGroup" page has been changed by ChristianGrobmeier:
https://wiki.apache.org/logging/AdminGroup?action=diff&rev1=5&rev2=6

Comment:
added MattSicker

   * IvanHabunek
   * ChristianGrobmeier
   * scottdeboy
+  * MattSicker

Apache Wiki | 30 Aug 05:18 2014
Picon

[Logging Wiki] Update of "Log4j2ReleaseGuide" by msicker

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 msicker:
https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=29&rev2=30

Comment:
add info about git and other things learned

  Once you've done this, take the following steps to perform a release:

   1. Edit {{{pom.xml}}} and change the {{{Log4jReleaseVersion}}} property to the version you are releasing.
-  1. Check out from https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk.
+  1. Make a fresh Git clone of the master branch of {{{https://git-wip-us.apache.org/repos/asf/logging-log4j2.git}}}
   1. Update {{{src/changes/announcement.vm}}}
   1. Run {{{mvn -P release-notes generate-resources}}} to create the release notes.
   1. Update {{{src/changes/changes.xml}}} with the release date.
 <at>  <at>  -61, +61  <at>  <at> 

      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.
      a. Provide a link to the tag, web site on http://people.apache.org, and the artifacts in the Nexus repository.
-     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.
+     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).
(Continue reading)

Matt Sicker | 22 Aug 21:10 2014
Picon

[ANN] Apache Log4j 2.0.2 released

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:


--
Matt Sicker <boards <at> gmail.com>
Apache Wiki | 17 Aug 06:43 2014
Picon

[Logging Wiki] Update of "Log4j2ReleaseGuide" by msicker

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 msicker:
https://wiki.apache.org/logging/Log4j2ReleaseGuide?action=diff&rev1=28&rev2=29

Comment:
add step for updating the announcement template

  
   1. Edit {{{pom.xml}}} and change the {{{Log4jReleaseVersion}}} property to the version you are releasing.
   1. Check out from https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk.
+  1. Update {{{src/changes/announcement.vm}}}
   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 {{{svn commit}}} to commit the {{{RELEASE-NOTES.txt}}} file that was just generated.

Matt Sicker | 5 Aug 19:47 2014
Picon

[ANNOUNCEMENT] Apache Log4j 2.0.1 released

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 patch release of Log4j 2.0 which contains numerous bug fixes. Version 2.0.1 is available now!

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:



--
Matt Sicker <boards <at> gmail.com>
Apache Wiki | 31 Jul 17:15 2014
Picon

[Logging Wiki] Update of "ContributorsGroup" by RalphGoers

Dear Wiki user,

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

The "ContributorsGroup" page has been changed by RalphGoers:
https://wiki.apache.org/logging/ContributorsGroup?action=diff&rev1=3&rev2=4

  #acl AdminGroup:read,write,admin,revert,delete All:read
  '''Contributors''' with permission to edit the Logging wiki – read, write, delete and revert pages or
individual changes. To be added to this group, please send a brief request to the
general.at.logging-dot-apache-dot-org mailing list including your wiki username. No mailing list
subscription required.

- Related: [[AdminGroup| Administrators]] with permission to grant privileges to Contributors, in
addition to being Contributors themselves.  NOTE: This list is not publicly viewable.
+ Related: [[AdminGroup|Administrators]] with permission to grant privileges to Contributors, in
addition to being Contributors themselves.  NOTE: This list is not publicly viewable.

   * AdminGroup
   * NickWilliams
   * rpopma
   * GaryGregory
+  * msicker

Matt Sicker | 31 Jul 14:52 2014
Picon

Request to be added to the Logging wiki

Ralph Goers | 17 Jul 07:26 2014

[ANNOUNCEMENT] Apache Log4j 2.0 released

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/

Ralph Goers | 26 Jun 01:05 2014

[ANNOUNCEMENT] Apache Log4j 2.0-rc2 released

The Apache Log4j 2 team is pleased to announce the Log4j 2.0-rc2 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.

It is the Log4j team's intention that this will be the final release candidate Log4j 2 before general
availability and
is being made available to encourage use and feedback from the community.

Changes in this version include:

New features:
o LOG4J2-675:  RollingFile and RollingRandomAccessFile now write the layout footer before rollover. 
o LOG4J2-674:  Made RollingFileAppender buffer size configurable. 
o LOG4J2-42:  Create an appender to route log events to the ServletContext log. 
o LOG4J2-655:  Add Vagrantfile for testing in GNU+Linux. 
o LOG4J2-654:  Add log4j-perf module to provide a home for all log4j performance tests.
        Add support for JMH microbenchmark performance tests. 
o LOG4J2-652:  Add support for default plugin values and attributes. 
o LOG4J2-598:  Add support for types other than String for plugin factory values/attributes. 
o LOG4J2-644:  Implement a SecureSocketAppender and secure server (SSL/TLS). 
o LOG4J2-629:  Document the system properties used in Log4J 2. 
o LOG4J2-595:  Introduce Java annotation processor as alternative plugin pre-caching mechanism. This is
available in the
          log4j-plugin-processor module. 
o LOG4J2-576:  Add org.apache.logging.log4j.Logger.getLevel(). 
o LOG4J2-439:  Add EncodingPatternConverter to escape newlines and HTML special characters. Thanks to
Bruce Brouwer. 
o LOG4J2-427:  Add support for configuration via YAML. Thanks to Alexander Reelsen. 

Fixed Bugs:
o LOG4J2-581:  RollingRandomAccessFile now writes the layout header after rollover. Thanks to Alexander
Khokhlov. 
o LOG4J2-622:  RollingFileManager now correctly honours the bufferedIO configuration after rollover.
Thanks to Farooq Khan. 
o LOG4J2-141:  Improved documentation regarding log4j status logger. Thanks to Joern Huxhorn. 
o LOG4J2-539:  Fixed issue with "Reconfigure using XML below" function in JMX Client GUI.
        ConfigurationSource is now a top-level class and can be obtained with Configuration.getConfigurationSource().
        LoggerContext.getConfiguration().getConfigurationSource() 
        provides a reliable public method for obtaining a logger context's configuration location and content.
Thanks to Colin Froggatt. 
o LOG4J2-619:  Invalid XML configuration files do not prevent the config file from being checked again.
Thanks to Scott Harrington. 
o LOG4J2-637:  JMX: Updating a Logger's level via jConsole now correctly takes effect. Thanks to Mansoor
Sajjad, Jon Wilmoth. 
o LOG4J2-668:  Correctly process log events when combining AsyncLoggers with AsyncAppender. 
o LOG4J2-669:  Prevent NPE when combining AsyncLoggers with AsyncLoggerConfigs. 
o LOG4J2-563:  FlumeAvroManager now always uses a client type of default_failover. Thanks to Michael
Friedmann. 
o LOG4J2-535:  Reset rollover time when size rollover is triggered. 
o LOG4J2-664:  Moved plugin cache file to META-INF for OSGi compatibility. 
o LOG4J2-640:  Fix NPE that can be caused by a null ThreadContextClassLoader. 
o LOG4J2-651:  Log4j 2 throws ArrayIndexOutOfBoundsException. 
o LOG4J2-620:  Perform reconfiguration in a separate thread to prevent deadlocks. 
o LOG4J2-639:  Prevent NPE in AsyncLogger and AsyncLoggerConfig if logger is used after log4j has been shut
down. Thanks to Mck SembWever. 
o LOG4J2-469:  FailoverAppender was not resetting its status after the primary appender recovered. 
o LOG4J2-623:  Generate MDC properties as a JSON map in JSONLayout. 
o LOG4J2-520:  Resolved issue where AsyncAppender dropped events if queue still contained
        events when application is stopped. Thanks to JavaTech, Andre Bogus. 
o LOG4J2-392:  Resolved a problem with the previous solution for LOG4J2-392 that resulted in dropped events
        when using AsyncLoggerConfig with slow appenders when application is stopped. Thanks to Andre Bogus. 
o LOG4J2-613:  The OSGi version of log4j-web imports Servlet 2.5 at minimum instead of 3.0. 
o LOG4J2-602:  Unit tests are now less verbose during the build process. 
o LOG4J2-570:  Fix shutdown thread memory leak in servlet containers. 
o LOG4J2-542:  Make Throwable transient in ThrowableProxy. 
o LOG4J2-440:  During shutdown, a NullPointerException could be thrown due to the NullConfiguration
class no longer being
        available to the ClassLoader. 
o LOG4J2-346:  Cyclic dependency with log4j-slf4j-impl in OSGi. 
o LOG4J2-345:  The log4j-1.2-api module didn't export any packages to OSGi. 
o LOG4J2-605:  Password data from the NoSQL plugins no longer shows up in cleartext in debug logging. 
o LOG4J2-448:  A StringIndexOutOfBounds exception could occur during property substitution. Thanks to
X86core. 
o LOG4J2-597:  StatusLogger was not skipping multiple instances of the FQCN class, causing messages from
classes in
        the Verbose list to be printed. 
o LOG4J2-564:  Renamed SLF4J logger class to Log4jLogger. 
o LOG4J2-579:  Rework Level comparison APIs. 
o LOG4J2-560:  SyslogAppenderTest and RFC5424LayoutTest were failing in Java 8. 
o LOG4J2-499:  Add equals and hashcode to Log4jLogEvent. 
o LOG4J2-378:  Add DateLookup and ThreadContextLookup to default lookups. 

Changes:
o LOG4J2-419:  Support default value for missing key in look ups with fallbacking to looking in the
properties map. Thanks to Woonsan Ko. 
o LOG4J2-554:  Allow configuration files to be located as Servlet Context resources. 
o LOG4J2-250:  Refactor Log4jLogEvent to lazily create ThrowableProxy. 
o LOG4J2-647:  Upgrade to Flume 1.5.0. 
o LOG4J2-646:  Merge the TLS Syslog appender into the Syslog appender. 
o LOG4J2-641:  Override commons-logging dependency version in tests. 
o LOG4J2-566:  Made RollingRandomAccessFileAppender buffer size configurable. Thanks to Luigi Alice. 
o LOG4J2-628:  Use Clock to generate all log event timestamps, not just for Async Loggers. 
o LOG4J2-617:  Update SLF4J to 1.7.7. 
o LOG4J2-616:  Update Jackson to 2.3.3. 
o LOG4J2-585:  Add support for multiple parents to Markers. Thanks to Bruce Brouwer. 
o LOG4J2-574:  Make Blocking the default WaitStrategy for Async Loggers. 
o LOG4J2-555:  Introduce ExtendedLogger interface to facilitate implementing and extending Loggers.
Thanks to Bruce Brouwer. 
o LOG4J2-561:  Allow spaces around commas in Configuration's package attribute. Thanks to vibin. 
o LOG4J2-547:  Have Logger API expose a PrintWriter instead of custom LoggerStream. Thanks to Bruce
Brouwer. 
o LOG4J2-496:  Allow header and footer to be specified as lookup patterns in PatternLayout. 
o LOG4J2-410:  SLf4JLogger is now Serializable. Thanks to Ivlin Zeng. 
o LOG4J2-468:  Add support to add a LoggerConfig. Document two ways to modify the configuration. 
o LOG4J2-582:  Rename org.apache.logging.log4j.core.net.SocketServer to TCPSocketServer and
refactor with UDP. 
o LOG4J2-592:  Update Jackson to 2.3.2 from 2.2.2. 

Apache Log4j 2.0-rc2 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/
Dominik Psenner | 29 May 14:07 2014
Picon

ApacheCon EU call for papers

Hey people,

 

this is a reminder that we’re in the final weeks of the ApacheCon EU call for paper and it will close at the end of the day of June 25th, whatever timezone is latest. We are still looking for presentations for this event. Check out this if you’re interested:

 

http://events.linuxfoundation.org/events/apachecon-europe/program/cfp

 

Best regards.

 

Dominik

Christian Grobmeier | 19 Feb 13:12 2014
Picon

[ANNOUNCEMENT] Nick Williams joins the Apache Logging PMC

Dear all,

please welcome Nick Williams as the lastest member of the 
Apache Logging PMC.

Nick made very valuable contributions esp to Log4j in the past
and the current PMC is very happy that he accepted our invitation.

Thanks Nick for your work so far and we are all looking forward
for more great times with you.

Regards,
Christian


Gmane