Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 236E4CF9E for ; Fri, 21 Jun 2013 19:24:00 +0000 (UTC) Received: (qmail 45856 invoked by uid 500); 21 Jun 2013 19:24:00 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 45819 invoked by uid 500); 21 Jun 2013 19:24:00 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 45811 invoked by uid 99); 21 Jun 2013 19:24:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 19:24:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of olivier.jaquemet@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bk0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 19:23:55 +0000 Received: by mail-bk0-f48.google.com with SMTP id jf17so3497544bkc.7 for ; Fri, 21 Jun 2013 12:23:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=azVchzYNTCxVdsC8PGs97iBaFw6+cE/8+cO1Rvk7kHU=; b=AVdx94+8NcZWFRRncMgOBB3TH5zXObFhXZzw/1FbMTYoHWIJvdggDSLeTtiOgvKr/u VUJ/XQSFoASp5pc7wDe9pEf1hiabRIHQ7H3Qb4vZcXjfXAUPDikQ4dmDWHkrzRzBnqOD /8TxhooHpZOoQPQNxZ7pjE1lJruEdXCdV17m/akJ1b8W56XEPQZnsUiUmbWbEK6u1Fsj c5ml3mhrtMYGNyr5yAYVe+5UJiu+Pik/TsPe9O2WtYegxum9kFhqfB1pWHtPOtlTqJ4X t5bRqf4mOlXyaXxI77810CI3SMTEWREuNiekaNHehzDS8FbQKV63cj7VgBZDSIk6UT6q mf0w== MIME-Version: 1.0 X-Received: by 10.204.226.201 with SMTP id ix9mr1983650bkb.157.1371842614322; Fri, 21 Jun 2013 12:23:34 -0700 (PDT) Received: by 10.204.21.205 with HTTP; Fri, 21 Jun 2013 12:23:34 -0700 (PDT) In-Reply-To: <83D94C77-D5DC-4C65-919C-5F7D4E6CF3CE@nicholaswilliams.net> References: <756E4597-C64E-4613-BECF-29BDF49BBC07@dslextreme.com> <83D94C77-D5DC-4C65-919C-5F7D4E6CF3CE@nicholaswilliams.net> Date: Fri, 21 Jun 2013 21:23:34 +0200 Message-ID: Subject: Re: Help for the javadoc fix From: Olivier Jaquemet To: Log4J Developers List Content-Type: multipart/alternative; boundary=485b3970cf4eb7278004dfaeff57 X-Virus-Checked: Checked by ClamAV on apache.org --485b3970cf4eb7278004dfaeff57 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ok, patch submitted for javadoc of log4j 1.2, in existing issue https://issues.apache.org/bugzilla/show_bug.cgi?id=3D55118 But : * I don't know how to ensure the build process uses the latest JDK so that the bug does not get reproduced on next site deploy * I could not find on the repo where the sites are hosted for log4j2 Olivier On Fri, Jun 21, 2013 at 8:25 PM, Nick Williams < nicholas@nicholaswilliams.net> wrote: > Also, note that there are already defects for both: > > https://issues.apache.org/jira/browse/LOG4J2-289 > https://issues.apache.org/bugzilla/show_bug.cgi?id=3D55118 > > Nick > > On Jun 21, 2013, at 1:17 PM, Ralph Goers wrote: > > Log4j 1.x uses bugzilla - > https://issues.apache.org/bugzilla/describecomponents.cgi?product=3DLog4j= . > Log4j 2 uses Jira - https://issues.apache.org/jira/browse/LOG4J2. > > For both the process is the same. > 1. Create a defect report. > 2. Check out the latest source. > 3. Create the fix. > 4. Create a patch using svn diff. > 5. Attach=E9 the patch to the defect report. > > Ralph > > > On Jun 21, 2013, at 11:10 AM, Olivier Jaquemet wrote: > > Hi all, > > Following my discussion on twitter with Christian Grobmeier : > https://twitter.com/OlivierJaquemet/status/347382534830710785 > > As I said, I am not familiar with the apache patches submission process > nor the repo. > But if someone point me in the right direction I'll be glad to help. > > Regards, > Olivier > > > > > > > --485b3970cf4eb7278004dfaeff57 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ok, patch submitted for javadoc of log4j 1.2, in existing issue

But : * I don't know how to ensure the build process uses the latest JDK so t= hat the bug does not get reproduced on next site deploy
* I could n= ot find on the repo where the sites are hosted for log4j2

Olivier

On Fri, Jun= 21, 2013 at 8:25 PM, Nick Williams <nicholas@nicholaswilliams= .net> wrote:

On Jun 21, 2013, at= 1:17 PM, Ralph Goers wrote:


For both the process is the same.
1. Create a= defect report.
2. Check out the latest source.
3. Crea= te the fix.
4. Create a patch using svn diff.
5. Attach= =E9 the patch to the defect report.

Ralph


On J= un 21, 2013, at 11:10 AM, Olivier Jaquemet wrote:

Hi all,

Following my discussion on twitter wit= h=A0Christian Grobmeier :

As I said, I am not familiar with the apache patches su= bmission process nor the repo.
But if someone point me in th= e right direction I'll be glad to help.

Regards,
Olivier







--485b3970cf4eb7278004dfaeff57--