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
contactUs.xml
<?xml version="1.0"?>
<document>
<properties>
<author email="cgu@apache.org">Ceki Gulcu</author>
<title>log4j project</title>
</properties>
<body>
<section name="Reporting tools">
<p>Bugs should be reported by using the
<a href="http://nagoya.apache.org/bugzilla">Apache Bug Database</a>.<br/>
Before reporting a problem, please <a href="http://nagoya.apache.org/bugzilla/query.cgi">check the database</a>
and the <a href="HISTORY">project history file</a> to see if the problem is already known.</p>
<p>Support requests should be sent to the log4j-user list (see below).</p>
</section>
<section name="Mailing lists">
<p>New releases and important bug-fixes are anounced at the
<em>log4j-announce</em> list. You can subscribe to the log4j-announce
list, or change your existing subscription <a
href="http://lists.sourceforge.net/mailman/listinfo/log4j-announce">online</a>.
The traffic on this list is extremely low and you are encouraged to
subscribe to this list if you are using log4j.</p>
<p>Discussion on log4j and logging in general are held on the
<em>log4j-user</em> mailing list. This list is <a
href="http://marc.theaimsgroup.com/?l=log4j-user&r=1&w=2">archived</a>.
To post a message to all its members, send email to <A
HREF="mailto:log4j-user@jakarta.apache.org">log4j-user@jakarta.apache.org</A>.
To subscribe to the log4j-users list send an email to <A
HREF="mailto:log4j-user-subscribe@jakarta.apache.org">log4j-user-subscribe@jakarta.apache.org</A>.</p>
<p>Development related discussions are held on the <em>log4j-dev</em> mailing
list. This list is <a href="http://marc.theaimsgroup.com/?l=log4j-dev&r=1&w=2">archived</a>. To post a message to all its members,
send email to <A
HREF="mailto:log4j-dev@jakarta.apache.org">log4j-dev@jakarta.apache.org</A>. To subscribe to the log4j-dev list send an email to <A
HREF="mailto:log4j-dev-subscribe@jakarta.apache.org">log4j-dev-subscribe@jakarta.apache.org</A>.</p>
<p>All developers are encouraged to subscribe to the
<em>log4j-cvs</em> list which will notify you of CVS commits to the
repository. This list is <a
href="http://marc.theaimsgroup.com/?l=log4j-cvs&r=1&w=2">archived</a>.
To post a message to all its members, send email to <A
HREF="mailto:log4j-cvs@jakarta.apache.org">log4j-cvs@jakarta.apache.org</A>. To
subscribe to the log4j-cvs list send an email to <A
HREF="mailto:log4j-cvs-subscribe@jakarta.apache.org">log4j-cvs-subscribe@jakarta.apache.org</A>.</p>
</section>
</body>
</document>