Scott Deboy | 1 Sep 04:23 2007

RE: Eliminating PluginConfigurator

It looks like Chainsaw is still at:
http://logging.apache.org/chainsaw/download.html

instead of:
http://logging.apache.org/log4j/docs/chainsaw/download.html

I also noticed the dependency listings at http://logging.apache.org/chainsaw/dependencies.html
don't resolve correctly.

Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:      503.224.7496
Cell:           503.997.1367
Fax:            503.222.0185

sdeboy <at> comotivsystems.com

www.comotivsystems.com

-----Original Message-----
From: Curt Arnold [mailto:carnold <at> apache.org]
Sent: Fri 8/31/2007 3:37 PM
To: Log4J Developers List
Subject: Re: Eliminating PluginConfigurator

On Aug 30, 2007, at 5:47 PM, Scott Deboy wrote:

(Continue reading)

Scott Deboy | 1 Sep 04:28 2007

RE: Eliminating PluginConfigurator

Correction - only http://logging.apache.org/log4j/companions/chainsaw is not resolving.

Scott Deboy
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201

Telephone:      503.224.7496
Cell:           503.997.1367
Fax:            503.222.0185

sdeboy <at> comotivsystems.com

www.comotivsystems.com

-----Original Message-----
From: Scott Deboy [mailto:sdeboy <at> comotivsystems.com]
Sent: Fri 8/31/2007 7:23 PM
To: Log4J Developers List
Subject: RE: Eliminating PluginConfigurator

It looks like Chainsaw is still at:
http://logging.apache.org/chainsaw/download.html

instead of:
http://logging.apache.org/log4j/docs/chainsaw/download.html

I also noticed the dependency listings at http://logging.apache.org/chainsaw/dependencies.html
don't resolve correctly.

(Continue reading)

Curt Arnold | 1 Sep 07:39 2007
Picon

Re: Eliminating PluginConfigurator


On Aug 31, 2007, at 9:23 PM, Scott Deboy wrote:

> It looks like Chainsaw is still at:
> http://logging.apache.org/chainsaw/download.html

That is expected.  The "new" Maven generated chainsaw content is  
below http://logging.apache.org/chainsaw.

On http://logging.apache.org/chainsaw/download.html, the links are to  
the old locations.  That should change when we get Maven building the  
webstart stuff.  Then we'd have redirects at the old locations  
pointing to the new locations.

>
> instead of:
> http://logging.apache.org/log4j/docs/chainsaw/download.html
>

I've put the old content up on http://people.apache.org/~carnold/ 
log4j/docs/index.html.

I reviewed the old site source and I didn't see that URL.  There was  
http://logging.apache.org/log4j/docs/chainsaw.html and http:// 
logging.apache.org/log4j/docs/install-chainsaw.html (which might have  
been blank).  I've added redirects for log4j/docs/chainsaw.html and  
log4j/docs/install-chainsaw.html to redirect to l.a.o/chainsaw/ 
index.html and for index.html, manual.html and download to redirect  
to the corresponding log4j/1.2 documents.

(Continue reading)

Scott Deboy | 1 Sep 07:47 2007

RE: Eliminating PluginConfigurator

Apologies - the old Chainsaw URL was http://logging.apache.org/log4j/docs/chainsaw.html, which now
redirects as expected.

Re: dependency listings - on page: http://logging.apache.org/chainsaw/dependencies.html

The first entry in the 'Dependency Listings' section is for Chainsaw 'companion' at: http://logging.apache.org:80/log4j/companions/chainsaw

Which doesn't exist.  The other links work.

Thanks

Scott

-----Original Message-----
From: Curt Arnold [mailto:carnold <at> apache.org]
Sent: Fri 8/31/2007 10:39 PM
To: Log4J Developers List
Subject: Re: Eliminating PluginConfigurator

On Aug 31, 2007, at 9:23 PM, Scott Deboy wrote:

> It looks like Chainsaw is still at:
> http://logging.apache.org/chainsaw/download.html

That is expected.  The "new" Maven generated chainsaw content is  
below http://logging.apache.org/chainsaw.

On http://logging.apache.org/chainsaw/download.html, the links are to  
the old locations.  That should change when we get Maven building the  
webstart stuff.  Then we'd have redirects at the old locations  
(Continue reading)

Curt Arnold | 1 Sep 19:06 2007
Picon

[ANNOUNCE] Apache log4j 1.2.15 and Apache log4j-extras 1.0 released

The Logging Services project is pleased to announce the release of  
Apache log4j 1.2.15.

Apache log4j 1.2.15 is a maintenance release of log4j 1.2 (http:// 
logging.apache.org/log4j/1.2).
The list of fixed issues is available at http://logging.apache.org/ 
log4j/1.2/changes-report.html.
The release may be downloaded from http://logging.apache.org/log4j/ 
1.2/download.html
and is also available in the master Maven repository (groupId: log4j,  
artifactId: log4j, version: 1.2.15).

The extras companion for log4j 1.2 (http://logging.apache.org/log4j/ 
companions/extras)
provides extra features to log4j 1.2 users and should work with log4j  
1.2.9 and later.
The companion may work with earlier versions of log4j 1.2
but that has not been tested.  Features provided by the extras  
companion include: parameterized
logging (with either java.text.MessageFormat or log4j 1.3 patterns),
Regular expression filters, rolling file appender with replaceable  
triggering and file
naming policies and an enhanced pattern layout with support for  
longer pattern names,
more abbreviation options, and time zone specification for date fields.
The release may be downloaded from
http://logging.apache.org/log4j/companions/extras/download.html
and is also available in the master Maven repository (groupId: log4j,  
artifactId: apache-log4j-extras,
version 1.0).
(Continue reading)

bugzilla | 3 Sep 08:08 2007
Picon

Bug report for Log4j [2007/09/02]

+---------------------------------------------------------------------------+
| Bugzilla Bug ID                                                           |
|     +---------------------------------------------------------------------+
|     | Status: UNC=Unconfirmed NEW=New         ASS=Assigned                |
|     |         OPN=Reopened    VER=Verified    (Skipped Closed/Resolved)   |
|     |   +-----------------------------------------------------------------+
|     |   | Severity: BLK=Blocker     CRI=Critical    MAJ=Major             |
|     |   |           MIN=Minor       NOR=Normal      ENH=Enhancement       |
|     |   |   +-------------------------------------------------------------+
|     |   |   | 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|New|Enh|2003-06-01|PreparedStatementAppender Enhancement             |
|22894|Opn|Nor|2003-09-02|Single backslash not accepted in File param value |
|22934|Opn|Nor|2003-09-04|org.apache.log4j.jmx is not compatible with JMX 1.|
|23329|Ass|Maj|2003-09-22|<logger> element in XML config should support reso|
|25355|New|Enh|2003-12-09|allow to require "TLS/SSL only" for outgoing mails|
|25747|New|Enh|2003-12-24|more explanations when hitting "WARN No appenders |
|26084|New|Nor|2004-01-13|Log Event detail panel does not show special chara|
|27363|New|Enh|2004-03-02|JNI based SyslogAppender                          |
|27367|New|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|
(Continue reading)

bugzilla | 3 Sep 14:47 2007
Picon

DO NOT REPLY [Bug 43295] New: - Zeroconf always uses default port (4560)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43295>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43295

           Summary: Zeroconf always uses default port (4560)
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: chainsaw
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: bugzilla <at> chrispaton.co.uk

I've just started using Zeroconf in my log4j enabled applications and am having
problems running more than application that uses Zeroconf on the same machine. I
hope this is the appropriate place to report this problem.

I downloaded the latest release of Chainsaw (2006-03-02), and added the provided
jmdns.jar and log4j-zeroconf.jar to my apps' classpath. I then amended my log4j
configuration to use the ZeroConfSocketHubAppender. One of my apps uses
log4j-1.2.8, the other uses the version that ships with JBoss 4.0.4.GA (the Jar
is un-numbered so I'm not sure exactly).

(Continue reading)

bugzilla | 3 Sep 17:20 2007
Picon

DO NOT REPLY [Bug 40212] - NullPointerException in getLogger when called from ShutdownHook

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40212>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40212

mail <at> dekies.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mail <at> dekies.de

--

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Scott Deboy | 3 Sep 19:44 2007

Broken links

If you google PaternLayout or any other core log4j class, the first reference is to this URL:

http://logging.apache.org/log4j/docs/api/org/apache/log4j/PatternLayout.html

However, that link is dead.  Can we redirect the old URL path to the new path?


Scott Deboy

bugzilla | 3 Sep 20:28 2007
Picon

DO NOT REPLY [Bug 43298] New: - log4j.dtd defines class attribute for category element, but not for logger.

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43298>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43298

           Summary: log4j.dtd defines class attribute for category element,
                    but not for logger.
           Product: Log4j
           Version: 1.2
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: log4j-dev <at> logging.apache.org
        ReportedBy: carnold <at> apache.org

--

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

Gmane