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>Contact us</title>
</properties>
<body>
<section name="Bug reporting">
<p>Bugs should be reported by using the
<a href="http://nagoya.apache.org/bugzilla">Apache Bug Database</a>.</p>
<p>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 not already known. After this verification step, you
are highly encouraged to send email to the <em>log4j-user</em>
mailing list (see below) describing the bug. Only after these
precautionary steps should you file a bug report.</p>
</section>
<section name="Mailing lists">
<p>New releases and important bug-fixes are announced 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. To subscribe to
this list send an e-mail 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. To subscribe to this list send an e-mail 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 the subscribers of CVS any
commits to the repository. To subscribe to this list send an e-mail
to <A
HREF="mailto:log4j-cvs-subscribe@jakarta.apache.org">log4j-cvs-subscribe@jakarta.apache.org</A>.
Committers <em>must</em> subscribe to this with their Apache mail
address.</p>
<p><b>To prevent spam, we expect you to be subscribed to a list before
posting to it. Otherwise, your mail needs to be approved by an
administrator which delays your posting and creates needless work for us.</b></p>
<p>Most Jakarta mailing lists, in particular the log4j mailing lists,
are archived. Some of the known archives are listed below:</p>
<ul>
<li>
<a href="http://www.mail-archive.com/">http://www.mail-archive.com</a>
</li>
<li>Full mbox archives of all Jakarta lists are available at <a
href="http://jakarta.apache.org/mail/">http://jakarta.apache.org/mail/</a>
</li>
<li>
<a href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</a>
</li>
</ul>
<p>Please do your best to ensure that you are not sending HTML or
"Stylelized" email to the list. If you are using Outlook or Outlook
Express or Eudora, chances are that you are sending HTML email by
default. There is usually a setting that will allow you to send "Plain
Text" email. </p>
</section>
</body>
</document>