The version of Apache log4j used by SoundHelix.
Clone
HTTPS:
git clone https://vervis.peers.community/repos/aEp6o
SSH:
git clone USERNAME@vervis.peers.community:aEp6o
Branches
Tags
- 1.3alpha-7
- CHAINSAW_2_SANDBOX_MERGE
- CORE_VERSION
- LEVEL_REPLACES_PRIORITY
- PREALPHA_1_3_AS_OF_2004_05_12
- PRE_CHAINSAW_MODEL_CONVERSION
- PRE_UGLI_MOVE
- TAG_CHAINSAW2_MOVE
- log4j-1.2.17
- log4j-1.2.17-rc1
- v1.3alpha8
- v1.3alpha8-temp
- v1_2_1
- v1_2_10-recalled
- v1_2_11
- v1_2_11_rc1
- v1_2_11rc3
- v1_2_12
- v1_2_12_rc1
- v1_2_12_rc2
- v1_2_12_rc3
- v1_2_12_rc4
- v1_2_12_rc5
- v1_2_12_rc6
- v1_2_13
- v1_2_13_rc1
- v1_2_13_rc2
- v1_2_13_site_update
- v1_2_14
- v1_2_14_maven
- v1_2_14_rc1
- v1_2_14_site_update
- v1_2_15
- v1_2_15_rc1
- v1_2_15_rc2
- v1_2_15_rc3
- v1_2_15_rc4
- v1_2_15_rc5
- v1_2_15_rc6
- v1_2_16
- v1_2_16_rc1
- v1_2_16_rc2
- v1_2_17
- v1_2_17-rc1
- v1_2_17_rc1
- v1_2_17_rc2
- v1_2_17_rc3
- v1_2_2
- v1_2_3
- v1_2_4
- v1_2_6
- v1_2_7
- v1_2_9
- v1_2_alpha0
- v1_2_alpha7
- v1_2beta1
- v1_2final
- v1_3alpha_1
- v1_3alpha_6
- v_1_0
- v_1_0_1
- v_1_0_4
- v_1_1
- v_1_1_1
- v_1_1_2
- v_1_1_3
- v_1_1_b1
- v_1_1b2
- v_1_1b3
- v_1_1b5
- v_1_1b6
- v_1_1b7
- v_1_2beta3
v_1_2beta3
:: docs
/
plan.html
<HTML>
<HEAD>
<TITLE>Release plan for log4j 1.2</TITLE>
</HEAD>
<BODY>
<center>
<h2>Workplan for log4j 1.2</h2>
</center>
<p>Here is my proposed plan for the next major log4j release. As
customary, there is no scheduled release date. It will be ready when
it is ready. Your comments and suggestions are most welcome.</p>
<p><TABLE border="1" cellpadding="3" cellspacing="2">
<TR>
<TH>Label</th>
<TH>Comment</th>
<TH>Volunteer</th>
<TH>Status</th>
</tr>
<TR bgcolor="DDDDDD">
<TD>More test cases</td>
<TD>We need more automated test cases to catch bugs as early
is possible.It is highly recommended to add a new test case
with each new feature or component.
</p>
</td>
<TD>All committers</td>
<td>ongoing effort</td>
</TR>
<TR >
<TD>Removal of deprecated methods</td>
<TD>Deprecated <code>setOption</code> and <code>getOption</code>
method should be removed.</td>
<TD>Ceki</td>
<td>done</td>
<TR bgcolor="DDDDDD">
<TD>JDBCAppender</td>
<TD>We currently have two competing JDBCAppenders: one by
Thomas Fenner and the other by Kevin Steppe. We should try
to get both authors to collaborate.
<p>We must be careful not to dismiss an implementation
without proper testing and due study. We should include at
least of one of these implemetation in the standard log4j
distribution. </p>
</td>
<TD>?</td>
<td>not started</td>
</tr>
<TR>
<TD>Log4j in applets</td>
<TD>In order to minimize network traffic, the size of log4j-core.jar
needs to be reduced to at most 50KB.
<p>Log4jME has been released. It's less than 20KB.</p>
</td>
<td>Ceki</td>
<TD>done</td>
</tr>
<TR bgcolor="DDDDDD">
<TD>Improved documentation</td>
<TD>Log4j documentation needs to be enhanced with configuration
examples and much more hand-holding.</td>
<TD>Ceki</td>
<td>under discussion</td>
</tr>
<TR>
<TD valign="top">Mapped Diagnostic Contexts</td>
<TD>Mapped Diagnostic Contexts are similar to the NDC
except that the MDC is a string to string map instead of
a stack that the user sets when entering a special
context. The <code>PatternLayout</code> has to be
enhanced to support this by extending the %x pattern to
accept an argument. Here is an example:
<pre>
ConversionPattern=3D%d %p %c %x{server} %x{host} - %m%n
</pre>
User code:
<pre>
{
MDC.put("server", "totoServer");
MDC.put("host", "someHost");
cat.debug("Hello");
}
</pre>
will print:
<pre>2000-01-24 10:00:00,000 DEBUG totoServer someHost - Hello</pre>
<p>To make MDCs truly user friendly <code>ThreadLocal</code> variables
are required. This will allow the MDC to be inherited by child
threads. <code>ThreadLocal</code> are only supported under JDK 1.2 and
above. In JDK 1.1, the MDC will not work but won't harm the user
application either.</p>
<TD>Ceki</td>
<td>done</td>
</td>
<TR bgcolor="DDDDDD">
<TD>Enhanced variable substitution support in DOMConfigurator</td>
<TD></td>
<TD>Ceki</td>
<td>done</td>
</tr>
<tr>
<td>FallbackErrorHandler</td>
<td>The FallbackErrorHandler implements the ErrorHandler
interface such that a secondary appender may be
specified. This secondary appender takes over if the primary
appender fails for whatever reason.
<p>The DOMConfigurator needs to be extended to support the
FallbackErrorHandler</p>
</td>
<td>Ceki</td>
<td>implemented, requires further testing</td>
</tr>
<tr bgcolor="DDDDDD">
<td>Review of the configure and watch architecture in configurators</td>
<td>This is a very useful feature and the current architecture is not very good.
<p>Contributions have been received by Mark Womack and others.</p>
<p>See
<br>http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg01390.html
<br>http://www.mail-archive.com/log4j-user@jakarta.apache.org/msg00666.html
<br/>http://marc.theaimsgroup.com/?t=101010070500002&r=1&w=2
</pre>
</p>
</td>
<td>?</td>
<td>not yet started</td>
</tr>
</TABLE>
</BODY>
</HTML>