Since properties are optional, I'd rather see them supported in the
standard log4j.dtd without having to do anything extra.
Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR 97201
Office: 503.224.7496
Direct Line: 503.821.6482
Cell: 503.997.1367
Fax: 50
On 08/08/2007, at 7:22 AM, Curt Arnold wrote:
The log4j 1.2 layout can produce non well formed content for some
atypical content (a message with an embedded -->, threads
containing & or >, etc). Plus it does not output MDC content
(log4j 1.3 does, but shares the other shortcomings). I've
+1
Can we 'svn move' trunk -> branches/BRANCH_1_3_ABANDONED ?
Then svn mv branches/log4j_12 > trunk?
1.3 has only ever had alpha releases. It's just a change management
issue we'll have to live with.
lets roll.
Paul
On 08/08/2007, at 7:32 AM, Curt Arnold wrote:
Log4j/trunk is no longer t
+1
Is there a convention describing an abandoned branch?
Scott Deboy
-Original Message-
From: Curt Arnold [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 07, 2007 2:32 PM
To: [email protected]
Subject: Rename log4j trunk?
Log4j/trunk is no longer the main development branch.
Log4j/trunk is no longer the main development branch. Renaming it
log4j/branches/v1_3-branch would eliminate mistaking it for the latest
and greatest. It may disrupt someone (we'd address gump as part of
the change), but I think they'd eventually have to deal with it.
I'm not sure if we s
The log4j 1.2 layout can produce non well formed content for some
atypical content (a message with an embedded -->, threads containing &
or >, etc). Plus it does not output MDC content (log4j 1.3 does, but
shares the other shortcomings). I've been tempted to overhaul it but
am hesitant to
