= Log4j wiki migrated to a [http://wiki.apache.org/logging-log4j/Log4JProjectPages new home]. This page is no longer updated! =
= Contributing code to the log4j project =
Have some code/patches you would like to contribute to the log4j project? Following the these guidelines does not guarantee that your code/patches will be accepted, but it will greatly increase the chances that they will be seriously considered and reviewed. All submissions are rigorously reviewed by the log4j committers for possible inclusion. Not all submissions are accepted, for various reasons. Some might be included in the log4j-sandbox instead of the core log4j release. Regardless, all submissions are encouraged. Much of today's log4j library was suggested and/or implemented by interested users.
#All submitted code that is meant for inclusion in log4j must contain a the Apache 1.1 license. Including this header at the beginning of all code files is usually sufficient:{{{ }}} }}}
#A detailed description of what the changes/classes are, why they are needed, and what they contribute. If we cannot understand what the changes are meant to fix/extend, then they certainly cannot be considered for inclusion. #Patch files generated from the current cvs versions. You can access the log4j cvs repository anonymously and get a copy of the current source see here. Once you have the latest sources from cvs, you can generate universal diff patches see here. #Submitted changes/classes must compile. Sorry if that seems obvious. #Submit changes to the log4j-dev email list. Or better yet, submit the changes via the Apache Bug Database as an enhancement request.