bugzilla | 1 Jul 10:38 2009
Picon

DO NOT REPLY [Bug 44932] improve DailyRollingFileAppender handling of rotation errors

https://issues.apache.org/bugzilla/show_bug.cgi?id=44932

apache <at> kastl-nbg.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|enhancement                 |critical

--- Comment #3 from apache <at> kastl-nbg.de  2009-07-01 01:38:52 PST ---
I lost a log file for a whole day due to issue P1, so I would say this is a
critical Bug not only an enhancement.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 1 Jul 15:00 2009
Picon

DO NOT REPLY [Bug 44932] improve DailyRollingFileAppender handling of rotation errors

https://issues.apache.org/bugzilla/show_bug.cgi?id=44932

apache <at> kastl-nbg.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |apache <at> kastl-nbg.de

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
manishmotwani | 1 Jul 21:02 2009
Picon

LocalizedLogger (enhancement)

I've written an enhancement to the localization support the generic Logger class provides.

A new LocalizedLogger overrides basic log4j logging methods (trace(), debug(), info(), warn(), error(), fatal()) to use a localization mechanism. Instead of the actual log messages, keys to localization log messages can be passed into these logging methods. Full parameterization is supported. If keys are not found in the ResourceBundle, they are logged directly, skipping the localization.


Internally, LocalizedLogger simply calls the l7dlog() method that already exists in Logger. LocalizedLogger is just a convenience class for applications that don't want to call this special method.


A LocalizationResourceBundle and a LocalizedLoggerFactory classes are also included. These helper classes provide easy integration with your application by simply changing the loggerFactory defined in the log4j configuration to point to this new LocalizedLoggerFactory.

I've attached an SVN diff that can be applied to log4j trunk.

Thanks,

Manish

Attachment (localization.patch): text/x-patch, 30 KiB

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
bugzilla | 2 Jul 12:20 2009
Picon

DO NOT REPLY [Bug 47465] New: Reading configuration files from a JAR locks the JAR file

https://issues.apache.org/bugzilla/show_bug.cgi?id=47465

           Summary: Reading configuration files from a JAR locks the JAR
                    file
           Product: Log4j
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: markt <at> apache.org

If a log4j configuration file is found by the classpath search inside a JAR
file, the file will be loaded from the JAR. However, the initial
URLConnection.getDefaultUseCaches() setting means that caching is used and the
JAR file is locked.

This is a particular problem for container environments like Tomcat, as it
prevents a web application from being removed. Whilst the workaround is simple
- don't put your log4j configuration in a JAR - it impacts a large number of
users.

I have a patch and test case for PropertyConfigurator. I still need to test
DOMConfigurator. I will update this bug report with the results of that test
(and a patch if necessary) later today.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 2 Jul 12:45 2009
Picon

DO NOT REPLY [Bug 47465] Reading configuration files from a JAR locks the JAR file

https://issues.apache.org/bugzilla/show_bug.cgi?id=47465

--- Comment #1 from Mark Thomas <markt <at> apache.org>  2009-07-02 03:45:08 PST ---
Created an attachment (id=23919)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23919)
Patch and test cases

Test cases to demonstrate the issue and a patch to fix the issue attached.

Note the test cases use files paths that work on my machine. These do not
appear to be consistent with the other test cases so a few tweaks may be
required.

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
Curt Arnold | 2 Jul 15:03 2009
Picon

Re: LocalizedLogger (enhancement)

There was discussion a few years back that was spread across several  
mailing lists on localization of logging, see
http://article.gmane.org/gmane.comp.jakarta.commons.devel/59103/ 
  for a jumping off place.  Searching for "localization" on the  
mailing list has two many false hits on Gump messages, searching for  
I18N and L7D hit more relevant matches.

Not having looked at your code, my instinct would be to go with a  
utility class approach like LogMF and LogSF in the extras companion.   
Where the call would end up like:

LogL7D.info(logger, ....)

Will try to review your code over the weekend.  Thanks for the  
submission.

On Jul 1, 2009, at 2:02 PM, manishmotwani <at> yahoo.com wrote:

> I've written an enhancement to the localization support the generic  
> Logger class provides.
>
> A new LocalizedLogger overrides basic log4j logging methods  
> (trace(), debug(), info(), warn(), error(), fatal()) to use a  
> localization mechanism. Instead of the actual log messages, keys to  
> localization log messages can be passed into these logging methods.  
> Full parameterization is supported. If keys are not found in the  
> ResourceBundle, they are logged directly, skipping the localization.
>
>
>
> Internally, LocalizedLogger simply calls the l7dlog() method that  
> already exists in Logger. LocalizedLogger is just a convenience  
> class for applications that don't want to call this special method.
>
>
> A LocalizationResourceBundle and a LocalizedLoggerFactory classes  
> are also included. These helper classes provide easy integration  
> with your application by simply changing the loggerFactory defined  
> in the log4j configuration to point to this new  
> LocalizedLoggerFactory.
>
> I've attached an SVN diff that can be applied to log4j trunk.
>
> Thanks,
>
> Manish
>
> <localization.patch>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
> For additional commands, e-mail: log4j-dev-help <at> logging.apache.org
manishmotwani | 2 Jul 18:03 2009
Picon

Re: LocalizedLogger (enhancement)

Curt,

Thanks for taking time out to review the code.

I forgot to mention another convenience feature:  The included LocalizationResourceBundle provides the ability to load localized log messages from multiple "logmessages_<LOCALE>.properties" files (e.g. logmessages_en_US.properties) from classpath. One of these files can be in each source directory and/or jar and all of them will be loaded automatically. The file name itself, of course, is also configurable via a system property. I'm not sure the extras utility classes provide the ability to load log messages from multiple files.

Besides, consid ering how light weight it is, it would be nice to have this convenience in core log4j, so we don't have to import multiple jars. Please feel free to rename the package from "localization" to "l18n" or something else.

Thanks!!

Manish

From: Curt Arnold <carnold <at> apache.org>
To: Log4J Developers List <log4j-dev <at> logging.apache.org>
Sent: Thursday, July 2, 2009 8:03:57 AM
Subject: Re: LocalizedLogger (enhancement)

There was discussion a few years back that was spread across several mailing lists on localization of logging, see http://article.gmane.org/gmane.comp.jakarta.commons.devel/59103/ for a jumping off place.  Searching for "localization" on the mailing list has two many false hits on Gump messages, searching for I18N and L7D hit more relevant matches.

Not having looked at your code, my instinct would be to go with a utility class approach like LogMF and LogSF in the extras companion.  Where the call would end up like:

LogL7D.info(logger, ....)

Will try to review your code over the weekend.  Thanks for the sub mission.



On Jul 1, 2009, at 2:02 PM, manishmotwani <at> yahoo.com wrote:

> I've written an enhancement to the localization support the generic Logger class provides.
>
> A new LocalizedLogger overrides basic log4j logging methods (trace(), debug(), info(), warn(), error(), fatal()) to use a localization mechanism. Instead of the actual log messages, keys to localization log messages can be passed into these logging methods. Full parameterization is supported. If keys are not found in the ResourceBundle, they are logged directly, skipping the localization.
>
>
>
> Internally, LocalizedLogger simply calls the l7dlog() method that already exists in Logger. LocalizedLogger is just a convenience class for applications that don't want to call this special method.
>
>
> A LocalizationResourc eBundle and a LocalizedLoggerFactory classes are also included. These helper classes provide easy integration with your application by simply changing the loggerFactory defined in the log4j configuration to point to this new LocalizedLoggerFactory.
>
> I've attached an SVN diff that can be applied to log4j trunk.
>
> Thanks,
>
> Manish
>
> <localization.patch>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
> For additional commands, e-mail: log4j-dev-help <at> logging.apache.org


---------------------------------------------------------------------
To unsubscr ibe, e-mail: log4j-dev-unsubscribe <at> logging.apache.org
For additional commands, e-mail: log4j-dev-help <at> logging.apache.org


bugzilla | 6 Jul 08:08 2009
Picon

Bug report for Log4j [2009/07/05]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker CRI=Critical  REG=Regression  MAJ=Major   |
|     |   |           MIN=Minor   NOR=Normal    ENH=Enhancement TRV=Trivial |
|     |   |   +-------------------------------------------------------------+
|     |   |   | Date Posted                                                 |
|     |   |   |          +--------------------------------------------------+
|     |   |   |          | Description                                      |
|     |   |   |          |                                                  |
|13099|Opn|Nor|2002-09-27|DOMConfigurator ignores category factory setting  |
|17887|Opn|Maj|2003-03-11|RollingFileAppender does not work for 10 threads  |
|20395|Inf|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|23329|New|Enh|2003-09-22|<logger> element in XML config should support reso|
|26084|Inf|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|Inf|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|Inf|Enh|2004-03-02|NetSendAppender                                   |
|28647|Ass|Enh|2004-04-28|Add "Flush on Level" capability to FileAppender   |
|29244|Inf|Nor|2004-05-27|Preserve XML content in log messages when using XM|
|29304|New|Nor|2004-05-30|Starting XMLSocketAppender from config file       |
|29305|New|Nor|2004-05-30|Chainsaw doesn't see locationinfo from XMLSocketRe|
|29735|New|Nor|2004-06-22|Receiver list display error  when receiver has no |
|30055|New|Nor|2004-07-12|Problem with registering Appenders with the same n|
|30407|Inf|Maj|2004-07-30|Externally rolled file problem                    |
|30888|New|Maj|2004-08-27|Chainsaw mixes files in same panel                |
|30890|New|Min|2004-08-27|Newly opened log file should get focus            |
|30892|New|Min|2004-08-27|Log files cannot be closed                        |
|31089|New|Nor|2004-09-07|Does not accept ISO8601 dates in focus field      |
|31178|Inf|Cri|2004-09-11|Exception using Chainsaw for simple debugging     |
|31179|Ass|Enh|2004-09-11|Implement Chainsaw as Eclipse stand-alone applicat|
|33278|New|Min|2005-01-27|NPE thrown durring daily log file rollover        |
|33493|Inf|Enh|2005-02-10|contribution to log4j: servlet diagnostic context |
|33717|New|Nor|2005-02-23|Leaving out %throwable in ConversionPattern adds t|
|34440|New|Nor|2005-04-13|sandbox:IMAppender - comma-seperated recipient lis|
|34491|Ver|Nor|2005-04-18|Missing include in build.jms target results in mis|
|34651|New|Enh|2005-04-27|allow for a header on top of every rolled file    |
|34738|New|Nor|2005-05-04|Chainsaw does not remember what Columns are select|
|34945|Inf|Nor|2005-05-17|ThrowableInformation has dubious Stack Trace extra|
|34974|Inf|Cri|2005-05-19|Exception when running a Pluglet                  |
|35180|New|Min|2005-06-02|Multiple lines "XML files (*.xml)" in drop down li|
|35239|Inf|Nor|2005-06-06|NullPointerException when saving displayed events |
|35563|Inf|Enh|2005-06-30|Syslog appender parametrability                   |
|35996|Inf|Enh|2005-08-03|Add support for ant-like <property> in log4j.xml  |
|36435|New|Enh|2005-08-31|Log4J RollingFileAppender under OpenVMS does not f|
|36654|Inf|Min|2005-09-14|Provide better error messages for "Please initiali|
|36789|Inf|Nor|2005-09-23|Empty control flow statement in org.apache.log4j.l|
|36860|New|Enh|2005-09-29|[jmx] Add ability to create a logger MBean for a n|
|37349|Ass|Nor|2005-11-03|DBAppender not working with jTDS driver           |
|37638|New|Nor|2005-11-25|logging doesn't fall back with FallbackErrorHandle|
|37734|Inf|Nor|2005-12-01|Customize Event ID and Event Category with NTEVent|
|37762|New|Enh|2005-12-02|RSSAppender or other approach.                    |
|38061|New|Nor|2005-12-28|Problem configuring an errorHandler using a proper|
|38363|Ass|Nor|2006-01-24|SecurityException during log output               |
|38394|Ver|Enh|2006-01-26|PropertySetter fails to print stacktrace if error |
|38395|Ver|Reg|2006-01-26|Unable to set threshold on appender via config fil|
|38406|Ver|Nor|2006-01-26|jdk1.4 dependencies in log4j 1.3 alpha            |
|38513|New|Nor|2006-02-05|[PATCH] Suggested unit test for JMSAppender       |
|38582|Ass|Nor|2006-02-08|Chainsaw does not include Receiver JavaDoc in dist|
|38590|Inf|Nor|2006-02-09|no space on device fails another instance         |
|38883|Opn|Nor|2006-03-07|LogFilePatternReceiver fails to process multi-line|
|38884|New|Nor|2006-03-07|null pointer exception displaying logs if number o|
|39690|Inf|Cri|2006-05-31|Initialization fail in J2EE Environment           |
|39691|Ass|Nor|2006-05-31|DBAppender doesn't log long events                |
|40068|New|Nor|2006-07-18|Add support for attach-on-demand API to chainsaw  |
|40124|New|Min|2006-07-27|startup (JWS) does not initialize ignored elements|
|40251|Opn|Min|2006-08-14|Hard coded JMX domain name for MBean instances    |
|40382|Inf|Maj|2006-09-01|Sysappender hangs during boot time on HP          |
|40385|Inf|Maj|2006-09-01|SocketServer cannot find config file when passed a|
|40472|New|Nor|2006-09-11|SettingsManager calls loadSettings with global set|
|40533|New|Nor|2006-09-18|Chainsaw not showing all logging statements       |
|40570|Inf|Blk|2006-09-21|RollingFileAppender does not rollover when the fil|
|40611|New|Trv|2006-09-27|Bad subclass example; NullPointerException in Logg|
|40736|Inf|Nor|2006-10-11|log4j delete permission denied                    |
|40889|Inf|Nor|2006-11-03|repeated entries in log after failure             |
|40990|Inf|Nor|2006-11-17|Cannot bind port or ip address for outgoing UDP so|
|41006|Inf|Enh|2006-11-20|Contributing XMLSocketHubReceiver                 |
|41214|Ass|Maj|2006-12-19|Deadlock with RollingFileAppender                 |
|41311|Inf|Min|2007-01-06|Please make TimeBasedRollingPolicy non-final?     |
|41316|New|Nor|2007-01-08|NPE when using RollingFileAppender in Tomcat.     |
|41547|Inf|Nor|2007-02-05|PropertyConfigurator and layout.contentType       |
|41799|New|Enh|2007-03-09|SyslogAppender should enable to customize Log4j.Le|
|41882|Inf|Nor|2007-03-18|IE7 problems with Log4J web site                  |
|41937|New|Nor|2007-03-23|Logs from some panels missing in custom expression|
|41980|Inf|Maj|2007-03-29|Log4j stop updating log file- version log4j-1.2.8 |
|42171|New|Nor|2007-04-19|SocketHubReceiver duplicates messages             |
|42189|Ass|Nor|2007-04-22|Add simple bridge for java.util.logging, with basi|
|42213|Opn|Blk|2007-04-24|log4j causing threads to stuck in weblogic        |
|42516|Inf|Nor|2007-05-24|Log4j failed to log file when packaged in Eclipse |
|42664|New|Enh|2007-06-14|JUL Appender                                      |
|42842|Opn|Nor|2007-07-09|Create a PUBLIC identifier for the log4j DTD      |
|42883|Opn|Nor|2007-07-12|'Welcome' and 'Drag & Drop' panels can't be hidden|
|42933|Inf|Maj|2007-07-18|IllegalStateException thrown from FileAppender.clo|
|43061|Opn|Enh|2007-08-08|Flush appender regularty                          |
|43148|Ass|Nor|2007-08-16|LogFilePatternReceiver depends on jakarta-oro, cou|
|43277|New|Nor|2007-08-31|Add LogMF.entering, .exiting and .throwing methods|
|43282|Ass|Nor|2007-08-31|Add OSGi packaging info to log4j and companions   |
|43313|Ass|Nor|2007-09-05|log4j 1.2.16 release considerations and discussion|
|43403|Inf|Nor|2007-09-16|PatternLayout: new format modifer: prefix if non-e|
|43619|New|Enh|2007-10-13|Simple proposal for pluggable sys-props resolvers |
|43637|Inf|Nor|2007-10-16|SocketAppender.append(LoggingEvent) calls the Erro|
|43728|Inf|Cri|2007-10-29|Log file loss when specified file is locked by ano|
|43736|Ass|Nor|2007-10-30|Chainsaw does not honor encoding when loading XML |
|43820|New|Enh|2007-11-08|[PATCH] Layered Configurator Patch                |
|43879|Inf|Nor|2007-11-16|FileAppender writes Header multiple times         |
|43911|Inf|Nor|2007-11-20|logfiles not getting rolled over with RollingFileA|
|43923|Inf|Min|2007-11-21|JBOSS specific information in javadocs            |
|44219|Inf|Nor|2008-01-13|'WARNING' for a log level is silently ignored/chan|
|44308|New|Enh|2008-01-28|[Patch] JMX component for managing Logger configur|
|44370|Inf|Reg|2008-02-06|MANIFEST.MF broken in log4j-1.2.15.jar            |
|44386|Opn|Nor|2008-02-10|NTEventLogAppender.dll for windows 64             |
|44526|Inf|Nor|2008-03-04|segmentation fault occuring when PropertyConfigura|
|44557|Inf|Nor|2008-03-07|no close call to Appender after replacing the root|
|44649|Inf|Nor|2008-03-20|JMS Hangs when a Root Appender                    |
|44700|Inf|Nor|2008-03-28|Log4J locks rolled log files                      |
|44727|Inf|Nor|2008-04-01|Add missing Logger#isErrorEnabled and isWarningEna|
|44834|Inf|Nor|2008-04-17|SimpleSocketServer looses buffered logs, produces |
|44839|Inf|Nor|2008-04-17|SyslogAppender logging to a UNIX domain socket    |
|44932|New|Cri|2008-05-05|improve DailyRollingFileAppender handling of rotat|
|44934|Inf|Enh|2008-05-05|add helper method to DailyRollingFileAppender to g|
|44945|New|Nor|2008-05-06|SyslogAppender not working                        |
|45029|Ass|Nor|2008-05-18|Additional unit tests for Filters in extras compan|
|45042|New|Nor|2008-05-19|Need a reliable way to detect misconfiguration    |
|45109|Inf|Nor|2008-05-31|SMTPAppender uses wrong property for mail server  |
|45165|Ass|Enh|2008-06-09|Multifile Appender                                |
|45231|Ass|Nor|2008-06-18|Clear appenders call on logger calls a helper whic|
|45236|Inf|Cri|2008-06-19|Wriring output to an out-dated file.              |
|45304|Inf|Nor|2008-06-29|using log4j with OAS for some reasone all the logg|
|45481|New|Trv|2008-07-25|Source contains unused imports                    |
|45482|Inf|Min|2008-07-25|Source contains unused variables                  |
|45629|New|Nor|2008-08-13|TopicConnection is not closed                     |
|45660|New|Enh|2008-08-20|NDC could remove Hashtable entry if Stack gets emp|
|45753|New|Nor|2008-09-06|Code contribution: BurstFilter for extras         |
|45781|New|Nor|2008-09-11|RollingFileAppender under Windows does not rotate |
|45855|New|Enh|2008-09-21|Add site/apt documentation for JULBridgeLogManager|
|45932|New|Nor|2008-10-01|Log4j JMX MBeans not cleaned up                   |
|45934|New|Enh|2008-10-02|FileAppender should use virtual-machine shutdown h|
|45939|New|Nor|2008-10-02|Cannot drop HierarchyDynamicMBean from LoggerRepos|
|46049|New|Enh|2008-10-21|Filter support in PropertyConfigurator            |
|46100|New|Enh|2008-10-27|NagiosAppender available for contribution         |
|46226|New|Min|2008-11-18|log4j.properties not using the right log level    |
|46260|Inf|Nor|2008-11-21|RollingFileAppender and Tomcat has a strange behav|
|46426|Ass|Nor|2008-12-20|Implement commons-logging interfaces natively in l|
|46514|New|Nor|2009-01-12|provide API to re-init log4j                      |
|46533|New|Enh|2009-01-14|Deamon Thread                                     |
|46539|New|Maj|2009-01-15|The QuietWriter class does not live up to its publ|
|46570|New|Nor|2009-01-20|DailyRollingFileAppender rolls logs into files dat|
|46573|New|Maj|2009-01-21|MDC attributes cant't be displayed on Chainsaw    |
|46574|New|Maj|2009-01-21|Log4j cant't hang on chainsaw if this one is resta|
|46592|New|Trv|2009-01-23|trim() on property file entries                   |
|46626|New|Enh|2009-01-29|Log4J 1.2.15 SyslogAppender doesn't not handle TAG|
|46691|New|Nor|2009-02-10|log4j file rolling over on restart of the server  |
|46723|New|Nor|2009-02-17|log4j subject line host expansion                 |
|46804|New|Enh|2009-03-05|create the method PropertyConfigurator.configureAn|
|46851|New|Nor|2009-03-13|DailyRollingFileAppender with DatePattern='.'yyyy-|
|46868|New|Nor|2009-03-17|SocketHUBAppender: Allow restriction of binding to|
|46878|New|Cri|2009-03-19|Deadlock in 1.2.15 caused by AsyncAppender and Thr|
|46941|New|Enh|2009-03-31|Sub Level Logging Technique                       |
|46983|New|Enh|2009-04-07|More Debug output for log4j auto-configure request|
|47004|New|Nor|2009-04-08|log messages occasionally sharing a line          |
|47014|New|Nor|2009-04-10|Method Name in log (%M) invalid for some callers w|
|47107|New|Nor|2009-04-27|add clear() method to Log4j's MDC class           |
|47123|New|Blk|2009-04-29|TimeBasedRollingPolicy appends logs into a old log|
|47141|Inf|Enh|2009-05-02|add getCyclicBuffer() method to log4j SMTPAppender|
|47164|New|Enh|2009-05-07|HTMLLayout replace newline with <BR>              |
|47208|New|Enh|2009-05-17|Better Default colours for Log Panel Color Filter |
|47210|New|Nor|2009-05-17|ignore not ignoring, yet "focus on" works         |
|47350|New|Nor|2009-06-10|ISO8601DateFormat and AbsoluteTimeDateFormat don't|
|47357|New|Min|2009-06-11|Declaring logger and category with same name cause|
|47465|New|Nor|2009-07-02|Reading configuration files from a JAR locks the J|
+-----+---+---+----------+--------------------------------------------------+
| Total  159 bugs                                                           |
+---------------------------------------------------------------------------+
bugzilla | 7 Jul 16:52 2009
Picon

DO NOT REPLY [Bug 46404] NPE when logging an AxisFault with SocketAppender

https://issues.apache.org/bugzilla/show_bug.cgi?id=46404

--- Comment #13 from Richard Abbuhl <rabbuhl <at> hotmail.com>  2009-07-07 07:52:29 PST ---
When will you create a log4j release which contains these commited fixes?

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
bugzilla | 9 Jul 00:31 2009
Picon

DO NOT REPLY [Bug 45855] Add site/apt documentation for JULBridgeLogManager

https://issues.apache.org/bugzilla/show_bug.cgi?id=45855

Brett Randall <javabrett <at> gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|log4j-dev <at> logging.apache.or |psmith <at> apache.org
                   |g                           |

--- Comment #2 from Brett Randall <javabrett <at> gmail.com>  2009-07-08 15:31:14 PST ---
Cleaning up some local edits in my checkouts, thought this doc patch might be
an easy commit :).

Best
Brett

--

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Gmane