Ralph Goers | 24 Oct 17:27 2014

[ANNOUNCEMENT] Apache Log4j 2.1 released

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

GA Release 2.1

Changes in this version include:

New features:
o LOG4J2-868:  Add ShutdownCallbackRegistry interface for customizable shutdown callback handling.
This is particularly
        useful for application servers that wish to integrate with Log4j 2. 
o LOG4J2-589:  Supported filtering on custom log levels in configuration. 
o LOG4J2-856:  Documentation: add sections on the JUL Adapter, IO Streams and NoSQL Appenders to the Maven
and Ivy page. 
o LOG4J2-848:  Add a Java lookup to provide nicely formatted runtime version information. 
o LOG4J2-809:  Move reflection utility class to API's private utility classes. 
o LOG4J2-833:  Documentation: added Runtime Dependencies link to left nav-bar on site. 
o LOG4J2-816:  Documentation: added section on XInclude to user manual Configuration page. 
o LOG4J2-547:  Add the Log4j IOStreams component. 
o LOG4J2-431:  Added Memory-Mapped File Appender. Thanks to Claude Mamo. 
o LOG4J2-827:  Support use of TypeConverter classes through the standard Plugin system. 
o LOG4J2-825:  Add simple validation constraint annotations for the Plugin system. 
(Continue reading)

Apache Wiki | 20 Oct 06:17 2014
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=30&rev2=31

  If the release fails after sending the vote email:
   1. Login to http://repository.apache.org using your ASF credentials. Select "Staging Repositories"
then check the org.apache.logging repository and drop it.
   1. Rename the release tag in Git to add {{{rcn}}} to the end of the tag. '''Note that this may not be possible in
Git depending on configuration'''
+ {{{
+ git tag log4j-n.n log4j-n.n-rcn
+ git tag -d log4j-n.n
+ git push origin :refs/tags/log4j-n.n
+ git push --tags
+ }}}
-  1. Reset the version numbers in all of the poms back to the release snapshot.
+  1.#3 Reset the version numbers in all of the poms back to the release snapshot.
   1. Restart the release process as a new release candidate.

Apache Wiki | 13 Oct 17:53 2014
Picon

[Logging Wiki] Update of "Log4j2AndHibernate4" by StefanBodewig

Dear Wiki user,

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

The "Log4j2AndHibernate4" page has been changed by StefanBodewig:
https://wiki.apache.org/logging/Log4j2AndHibernate4?action=diff&rev1=1&rev2=2

Comment:
typo spetted by Dominik Psenner

   * add the log4j 2.x slf4j binding and slf4j-api to your classpath as well and set the system property
`org.jboss.logging.provider` to `slf4j` - setting the property explicitly bypasses the "logback is
there" check
   * override Hibernate's dependency to use jboss-logging 3.2.0.Beta1, add the log4j 1.x logging bridge to
your classpath as well and set the system property `org.jboss.logging.provider` to `log4j` - this
doesn't seem to work with any 3.1.x version of jboss-logging

- Things get even more complex if you add a non-default connection pool to Hibernate.  c3p0 prior to
0.9.5pre2 will only log to log4j 1.x so using the log4j 1.x logging bridge is your only option.  Later
versions of c3po added support for slf4j as well.
+ Things get even more complex if you add a non-default connection pool to Hibernate.  c3p0 prior to
0.9.5pre2 will only log to log4j 1.x so using the log4j 1.x logging bridge is your only option.  Later
versions of c3p0 added support for slf4j as well.

Apache Wiki | 13 Oct 14:15 2014
Picon

[Logging Wiki] Update of "Log4j2AndHibernate4" by StefanBodewig

Dear Wiki user,

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

The "Log4j2AndHibernate4" page has been changed by StefanBodewig:
https://wiki.apache.org/logging/Log4j2AndHibernate4

New page:
As of this writing Hibernate 4.3.6.Final is the current version of Hibernate and it uses jboss-logging
Version 3.1.3.GA for logging.  jboss-logging 3.2.0.Beta2 will support log4j 2.x natively and no
additional configuration will be required, but it hasn't been released, yet.  Once it has been released,
most information on this page will become obsolete.

As a sidenote: jboss-logging 3.2.0.Beta1 claims to support log4j 2.x natively but was based on beta
releases of log4j 2.x - due to a [[https://issues.jboss.org/browse/JBLOGGING-107|backwards
incompatible change in log4j 2.x after its beta]] jboss-logging 3.2.0.Beta1 doesn't work with the final
release of log4j 2.x.

jboss-logging is yet another layer on top of popular logging frameworks.  You can configure which logging
framework it should delegate to using the system property `org.jboss.logging.provider`, if it is not
set its discovery algorithm will try
 * jBoss' own logging implementation
 * log4j 2.x - starting with 3.2.0.Beta2
 * log4j 1.x - only if some internal log4j classes can be found
 * slf4j - only if logback is on the classpath as well
 * java.util.logging

in that order.  The possible values for the system property are `jboss`, `log4j2`, `log4j`, `slf4j` and `jdk`.

In order to use log4j2 with jboss-logging prior to 3.2.0.Beta2 you have two choices
(Continue reading)

Apache Wiki | 13 Oct 13:23 2014
Picon

[Logging Wiki] Update of "log4j2" by StefanBodewig

Dear Wiki user,

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

The "log4j2" page has been changed by StefanBodewig:
https://wiki.apache.org/logging/log4j2?action=diff&rev1=4&rev2=5

  
   * Log4j2ReleaseGuide - The steps required to perform a Log4j 2 release.

+ == Integration ==
+ 
+  * Log4j2AndHibernate4 -  Making Hibernate 4.x use Log4j 2.x
+ 
  == Ideas ==

   * Build a NoSQL Appender, maybe with AppScale: http://appscale.cs.ucsb.edu/datastores.html
Inspiration came from the log4j1 appender for redis: https://github.com/pavlobaron/log4j2redis

Apache Wiki | 13 Oct 09:39 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=6&rev2=7

Comment:
added StefanBodewig

   * ChristianGrobmeier
   * scottdeboy
   * MattSicker
+  * StefanBodewig

Stefan Bodewig | 13 Oct 06:30 2014
Picon

[wiki] Please Add Me To ContributorsGroup

Hi

my account is StefanBodewig and in order for me to change anything a
member of the admin group must add me to this page:
https://wiki.apache.org/logging/ContributorsGroup

Stefan

Apache Wiki | 13 Oct 06:05 2014
Picon

[Logging Wiki] Update of "FrontPage" by GaryGregory

Dear Wiki user,

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

The "FrontPage" page has been changed by GaryGregory:
https://wiki.apache.org/logging/FrontPage?action=diff&rev1=23781&rev2=23782

   * See HelpForBeginners to get you going, HelpContents for all help pages.
   * For customizing MoinMoin's language support see HelpOnLanguages.

- To learn more about what a WikiWikiWeb is, read about MoinMoin:WhyWikiWorks and the
MoinMoin:WikiNature. Also, consult  [[http://www.jocurile.us/jocuri-cu-masini/|jocuri cu
masini]] the HelpMiscellaneous/FrequentlyAskedQuestions page.
+ To learn more about what a WikiWikiWeb is, read about MoinMoin:WhyWikiWorks and the
MoinMoin:WikiNature. Also, consult the HelpMiscellaneous/FrequentlyAskedQuestions page.

- This wiki is powered by  [[http://www.profi-fachuebersetzungen.de|√úbersetzung]] and [[http://moinmo.in/|MoinMoin]].
+ This wiki is powered by [[http://www.faresoldisuinternet.com|Fare Soldi Su Internet]],
[[http://carinsurancecomparisonshelp.com|car insurance comparisons]] and [[http://moinmo.in/|MoinMoin]].

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>

Gmane