Added: logging/site/trunk/docs/log4net/src/contributing.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/log4net/src/contributing.html?view=auto&rev=559716 ============================================================================== --- logging/site/trunk/docs/log4net/src/contributing.html (added) +++ logging/site/trunk/docs/log4net/src/contributing.html Wed Jul 25 23:41:40 2007 @@ -0,0 +1,499 @@ + + + + + + + + + + + + + + Apache log4net - + Apache log4net: Contributing to log4net Development + + + + + + + + +
+ +
+
+
+ + + + + + + +

Contributing to log4net Development

+ + + + + +

Developer Mailing List

+

+ All discussion relating to log4net development takes place on this list. All SVN checkin + notifications are also copied to this list. +

+ +

Mailing List Archives

+

+ You can browse the mailing list archives at the following locations: +

+ + +
+ +

Subscribe

+ + Subscribe to either the list or to the digest list: + + + +
+ +

Unsubscribe

+ + To unsubscribe send an email to the relevant email address: + + + +
+ +

Posting

+ + Most of the guidelines for the log4net-user list also apply to the dev list. + Please have a quick read through the guidelines, thanks. + + + + To prevent spam, we require you to be subscribed to the list before posting to it. + + +

+ This is the log4net developer list, it holds discussions relating to the + development of log4net not the use of log4net. If you have a question that begins + with the word "How" or you are unsure as the the appropriate list to post to then + you probably want to start with the log4net-user list. +

+ +

+ Post to the list by sending mail to + log4net-dev@logging.apache.org. +

+
+
+ +

Source Access

+

+ The source for log4net is held in the Apache Subversion source code control repository. +

+ +

Browsing SVN

+

+ Browse log4net + SVN repository using ViewCVS. +

+
+ +

Anonymous SVN Access

+

+ Anyone can checkout source code from our anonymous SVN + server. To do so, simply use the following command (if you are + using a GUI SVN client, configure it appropriately). +

+ +

+ Checkout the logging/log4net module. +

+ +
+svn checkout http://svn.apache.org/repos/asf/logging/log4net/trunk log4net
+ +

+ If you are not familiar with SVN, the Apache + Source Code Repositories + page has links to more information on SVN. +

+
+ +
+ +

Issue Tracking

+

+ Many bugs reported end up not being a bug in the log4net code, + but are due to incorrect configuration, problems caused by installed applications, + the operating system, etc. +

+

+ Before reporting a bug please make every effort to investigate and resolve the problem yourself. + Just reporting a bug will not fix it. A good bug report includes a detailed + description of the problem and a succinct test case which can reproduce the problem. +

+

+ Before reporting an issue please investigate the following information sources for + a potential resolution. +

+ + + Before reporting a bug, you are advised to discuss it on the relevant mailing list first. + + + Search the bug database to see if the bug + you are seeing has already been reported. If it has been reported then you can vote for the issue. + + +

Reporting an Issue

+ + If after you have exhausted all other resources to resolve a problem you may want to file a bug report. + Please make sure the problem is a bug in Logging and not a bug in your application. + + + Please make sure you provide as much information as possible. Its very hard to fix a bug if the person + looking into the problem can't reproduce it. Here is a listing of information which should be included: + +
    +
  • Version - log4net version, or if from a nightly build, version and date of build.
  • +
  • Application Type - Assembly type, i.e. exe or dll, and how your code is launched, e.g. console application, windows application, ASP.NET project, COM+ hosted object, etc...
  • +
  • Framework - The .NET framework running the application, name (e.g. MS .NET, Mono, SSCLI) and version.
  • +
  • Platform - Computer operating system, version, and hardware platform in use.
  • +
  • Configuration - Attach configuration files if they would help track down the bug.
  • +
  • Log Files - Review your logs files, produced with internal log4net debug enabled. Submit any relevant sections of the log which help document the bug.
  • +
  • Stack Traces - Any stack traces generated by the bug, if any.
  • +
  • Example - Example configuration files or web applications which demonstrate the bug. When submitting an example which reproduces the bug, please try to make it as simple as possible.
  • +
  • Bug Fix Patch - A patch created using diff -u which fixes the bug. (If you have found a bug fix which can be applied to the code).
  • +
  • Description of the Bug - A description of the bug, include observed as well as expected behavior.
  • +
  • Miscellaneous - Any other information you feel will help track down the problem.
  • +
+ + Just reporting a bug will not fix it. A good bug report includes a detailed description of the + problem and a succinct test case which can reproduce the problem. The very best sort of report + includes an NUnit testcase which reproduces the issue, this means that we can fix it and that we can + be sure that it stays fixed in future! + + + Report a log4net issue here. You will need to login to JIRA before you can submit an issue. + +
+
+ +

Contributing Patches

+ + Before starting to work on a patch it is probably a good idea to join the log4net-dev + mailing list to check that equivalent or complementary work is not already underway. + + + Currently the only supported way of submitting patches to log4net + is via the JIRA issue tracking system. + + + The preferred method of generating a patch is a unified context diff against + the latest development version in SVN. To do this you should do the following: + +
    +
  • + + Get the latest version of the code from SVN, see the section above on + Anonymous SVN Access for details on how to obtain the SVN version. + +
  • +
  • + + Make your code changes to the log4net source. Please follow existing + code styles where possible. If adding new API methods or classes then + these should be appropriately documented with code comments. + Contributions intended for inclusion in ASF products must be licensed + to ASF under the terms of the + Apache Software License. + +
  • +
  • + + Generate a unified context diff for the files you have changed. Run the + svn diff > patch-file command from the root of the log4net + codebase to generate a diff file. + +
  • +
  • + + If you have added new files these will not be included in the diff. You + will need to attach these files separately. + +
  • +
+ + If you are not using SVN then you can still generate a unified context diff + using the diff GNU tool with the -u command line options. + The GNU tools are available for Windows as part + of the Cygwin package. + + + If you are unable to generate a diff please submit each file separately and place + block comments around each code change to highlight the differences. + + + + In order to submit your patch please follow the following steps: + +
    +
  • + + Create a new issue for your patch. On the + log4net issues home page + select the Create New Issue from the menu bar. You will need to be logged + into JIRA in order to create an issue. + +
  • +
  • + + Select the issue type as appropriate. + +
  • +
  • + + Prefix the summary with [PATCH]. Enter a description of the changes made, + new features, or bug fixes in your patch. + +
  • +
  • + + Once the issue has been created you can attach your patch file to the issue + by selecting the Attach file to this issue operation from the left hand + menu. When attaching your patch you must select the Grant license to ASF for + inclusion in ASF works option. When attaching a patch please include in the + description the baseline version of log4net you used to build your patch, if against + an SVN version please include the version number and if from a tag or branch include + the repository path. + +
  • +
  • + + If you have other files to attach, e.g. you have added new files to log4net, then + attach each file separately. Please include in the description the name of the file + attached and the path it should live in the project. + +
  • +
+ + A notification will be sent to the log4net-dev list once you have created your issue, + however it may also be worth mailing the log4net-dev list to encourage the project + committers to apply your patch, or at least find out when they may do so. + +
+ + +
+ + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/log4net/src/contributing.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/log4net/src/downloads.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/log4net/src/downloads.html?view=auto&rev=559716 ============================================================================== --- logging/site/trunk/docs/log4net/src/downloads.html (added) +++ logging/site/trunk/docs/log4net/src/downloads.html Wed Jul 25 23:41:40 2007 @@ -0,0 +1,251 @@ + + + + + + + + + + + + + + Apache log4net - + Apache log4net: Downloads + + + + + + + + +
+ +
+
+
+ + + + + + + +

log4net Downloads

+ +

Project Status

+

+ log4net has graduated from the Incubator project, however at the time + the following releases were made, log4net was still undergoing incubation, + therefore these releases are not officially endorsed by the ASF. +

+

+ Future releases of log4net will be officially endorsed by the ASF. +

+
+ +

Stable Releases

+

+ The following stable releases are available: +

+ + +
+ + + +

Archive Releases

+ + + + Previous releases of log4net are available from the sourceforge site: + + + +
+ +
+ + + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/log4net/src/downloads.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/log4net/src/history.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/log4net/src/history.html?view=auto&rev=559716 ============================================================================== --- logging/site/trunk/docs/log4net/src/history.html (added) +++ logging/site/trunk/docs/log4net/src/history.html Wed Jul 25 23:41:40 2007 @@ -0,0 +1,230 @@ + + + + + + + + + + + + + + Apache log4net - + Apache log4net: Project History + + + + + + + + +
+ +
+
+
+ + + + + + + +

log4net Project History

+ +

+ The log4net project was started by Neoworks Limited + in June 2001. It was created as an internal project within Neoworks to port the Apache + log4j code base to the Microsoft .NET Framework. The code base was initially branched + from a pre-alpha log4j 1.2. +

+ +

+ In July 2001 a Sourceforge project was started + and log4net was published under the Apache Software License. The first public release of + log4net was made in September 2001. A further 10 releases were made on the sourceforge + site. +

+ +

+ In December 2003 the Apache Logging Services project was created. + In February 2004 log4net was donated by Neoworks to the Apache Software Foundation + to become a member of the Logging Services project. +

+ +

+ In February 2007 log4net graduated from the Apache Incubator project to become a + fully fledged Apache project. Apache log4net is a subproject of the Logging Services project. +

+ +
+ + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/log4net/src/history.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/log4net/src/index.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/log4net/src/index.html?view=auto&rev=559716 ============================================================================== --- logging/site/trunk/docs/log4net/src/index.html (added) +++ logging/site/trunk/docs/log4net/src/index.html Wed Jul 25 23:41:40 2007 @@ -0,0 +1,308 @@ + + + + + + + + + + + + + + Apache log4net - + Apache log4net: Home + + + + + + + + +
+ +
+
+
+ + + + + + + +

About Apache log4net

+ +

Introduction

+

+ log4net is a tool to help the programmer output log statements to a variety + of output targets. log4net is a port of the excellent log4j framework to the + .NET runtime. We have kept the framework similar in spirit to the original log4j + while taking advantage of new features in the .NET runtime. + For more information on log4net see the features document. +

+ +

+ log4net is part of the Apache Logging Services + project. The Logging Services project is intended to provide cross-language logging + services for purposes of application debugging and auditing. +

+
+ +

Contributors

+ +

Active Committers

+ +
    +
  • + + Curt Arnold + +
  • +
  • + + Nicko Cadell + +
  • +
  • + + Niall Daley + +
  • +
  • + + Gert Driesen + +
  • +
  • + + Ron Grabowski + +
  • +
+ +
+ +

Community Contributors

+ +
    +
  • + + Julian Biddle + +
  • +
  • + + Daniel Cazzulino + +
  • +
  • + + Aspi Havewala + +
  • +
  • + + Rick Hobbs + +
  • +
  • + + Lance Nehring + +
  • +
  • + + Angelika Schnagl + +
  • +
  • + + Edward Smit + +
  • +
  • + + Douglas de la Torre + +
  • +
  • + + Thomas Voss + +
  • +
+
+ +
+ +
+ + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/log4net/src/index.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/log4net/src/license.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/log4net/src/license.html?view=auto&rev=559716 ============================================================================== --- logging/site/trunk/docs/log4net/src/license.html (added) +++ logging/site/trunk/docs/log4net/src/license.html Wed Jul 25 23:41:40 2007 @@ -0,0 +1,438 @@ + + + + + + + + + + + + + + Apache log4net - + Apache log4net: License + + + + + + + + +
+ +
+
+
+ + + + + + + +

Apache log4net License

+ +

Current License

+

+ The Apache Software License Version 2.0 applies to all releases of + log4net starting with log4net 1.2.1. +

+ +
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+
+                
+ +

+ The License is accompanied by this NOTICE: +

+ +
+   **
+   **  NOTICE file corresponding to the section 4 (d) of the Apache License, 
+   **  Version 2.0, in this case for the Apache log4net distribution.
+   **
+
+   Please read the LICENSE files present in the root directory of this 
+   distribution.
+
+   Apache log4net
+   Copyright 2001-2007 The Apache Software Foundation
+
+   This product includes software developed at
+   The Apache Software Foundation (http://www.apache.org/).
+
+                
+
+ +
+ + + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/log4net/src/license.html ------------------------------------------------------------------------------ svn:mime-type = text/html Added: logging/site/trunk/docs/log4net/src/release/building.html URL: http://svn.apache.org/viewvc/logging/site/trunk/docs/log4net/src/release/building.html?view=auto&rev=559716 ============================================================================== --- logging/site/trunk/docs/log4net/src/release/building.html (added) +++ logging/site/trunk/docs/log4net/src/release/building.html Wed Jul 25 23:41:40 2007 @@ -0,0 +1,357 @@ + + + + + + + + + + + + + + Apache log4net - + Apache log4net: Building log4net + + + + + + + + +
+ +
+
+
+ + + + + + + +

Building log4net

+ + +

+ The log4net release builds are built using NAnt. Log4net can also be built + using Visual Studio .NET 2002, 2003, or 2005. +

+

+ To build a release build of log4net you will need to create a strong + name key file. See the Strong Name section below. +

+ +

Visual Studio

+

+ Visual Studio .NET 2002, 2003 and 2005 are supported build platforms for log4net. +

+ +

Visual Studio .NET 2002

+

+ The log4net distribution includes a solution and project file + for Visual Studio .NET 2002. Open the log4net.sln + from the src directory in the distribution. +

+

+ The log4net project requires only the following references: +

+
    +
  • System
  • +
  • System.Data
  • +
  • System.Web
  • +
  • System.XML
  • +
+
+ +

Visual Studio .NET 2003

+ + Open the Visual Studio .NET 2002 solution file as above. + Visual Studio will convert the solution and project files + to Visual Studio .NET 2003 format. + + + After converting the log4net project you must change the + Conditional Compilation Constants specified for the + log4net project. Open the project properties dialog and + select the Configuration Properties/Build sheet. + Replace the NET_1_0 constant with NET_1_1. + Remember to do this for both Debug and Release configurations. + + + The log4net project file is not suitable for building log4net + for the .NET Compact Framework. To build for the Compact Framework + you must create a new C# project for Smart Devices. Configure the + project as a library project. Add all the C# files from the + src directory in the distribution. + +
+ +

Visual Studio 2005

+ + Open the Visual Studio .NET 2002 solution file as above. + Visual Studio will convert the solution and project files + to Visual Studio .NET 2003 format. + +

+ After converting the log4net project you must change the + Conditional compilation symbols specified for the + log4net project. Open the project properties page and + select the Build sheet. + Replace the NET_1_0 symbol with NET_2_0. + Remember to do this for both Debug and Release configurations. +

+

+ In addition the log4net project requires the following new references: +

+
    +
  • System.Configuration
  • +
+ + The log4net project file is not suitable for building log4net + for the .NET Compact Framework. To build for the Compact Framework + you must create a new C# project for Smart Devices. Configure the + project as a library project. Add all the C# files from the + src directory in the distribution. + +
+
+ +

NAnt

+

+ The log4net distribution is built using the NAnt tool. + A recent NAnt version 0.85 nightly build is required to build log4net, this is + available from nant.sourceforge.net. +

+

+ To support building log4net for the SSCLI framework the NAnt configuration + files need to be updated to specify the SSCLI framework directory. +

+

+ To build log4net from the command line, change directory to the root of the + log4net distribution, ensure that the nant executable is in the + PATH, and then run the following command: +

+
+nant -buildfile:log4net.build compile-all
+

+ This command will build log4net for all the supported frameworks + that are available on the current machine. To list all the build + targets that are available run the following command: +

+
+nant -buildfile:log4net.build -projecthelp
+

+ Under windows the build.cmd can be used + to script the nant build. This can be called from a different + directory and will locate the correct log4net.build file to use. + For example: +

+
+build.cmd compile-all
+
+ +

Strong Name

+

+ In order to build the Release builds of log4net a Strong + Name key is required. +

+

+ Use the sn.exe tool in the + .NET Framework SDK to generate a strong name key pair. +

+
+sn -k log4net.snk
+

+ The log4net.snk file should be placed in the root of the + log4net distribution, in the same folder as the log4net.build + file. +

+
+ +

SDK Reference

+

+ NDoc 1.3 is used to build the log4net SDK documentation. + NDoc is available from ndoc.sourceforge.net. +

+
+ +

HTML Documentation

+

+ The log4net HTML documentation is built using Velocity. + The source are XML files in the xdocs/src directory. + Building the documentation requires Java, Ant, and Velocity. + Run ant from within the xdocs directory. +

+
+ +
+ + +
+
+
+
+
+ + + Propchange: logging/site/trunk/docs/log4net/src/release/building.html ------------------------------------------------------------------------------ svn:mime-type = text/html