https://svn.apache.org/repos/asf/logging/log4j/log4j2/
On Jun 21, 2013, at 2:23 PM, Olivier Jaquemet wrote: > Ok, patch submitted for javadoc of log4j 1.2, in existing issue > https://issues.apache.org/bugzilla/show_bug.cgi?id=55118 > > 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 > <[email protected]> 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=55118 > > 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=Log4j. >> 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é 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 >>> >>> >>> >>> >> > >
