I downloaded: http://people.apache.org/~nicko/log4net/test-build/incubating-log4net-1.2.10.zip
unzipped it and ran "build.cmd" on my Windows XP system with both 1.1 and 2.0 of the framework installed. This is part of the output from the build.cmd file: " C:\incubating-log4net-1.2.10>build LOG4NET_DIR is C:\incubating-log4net-1.2.10 NANTEXE_PATH is nant.exe BUILD_FILE is C:\incubating-log4net-1.2.10\log4net.build NAnt 0.85 (Build 0.85.1932.0; rc3; 4/16/2005) Copyright (C) 2001-2005 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/incubating-log4net-1.2.10/log4net.build Target framework: Microsoft .NET Framework 1.1 Target(s) specified: compile-all " I saw this warning towards the end: " compile-net-1.1: [echo] Key file not found. You can generate a key file by running 'sn -k lo g4net.snk'. [echo] The generated key file should be stored in the log4net base director y. " which was caused by me not calling the sn command to generate a key file. This is output of files in the \bin directory: C:\incubating-log4net-1.2.10\bin\cli C:\incubating-log4net-1.2.10\bin\mono C:\incubating-log4net-1.2.10\bin\net C:\incubating-log4net-1.2.10\bin\netcf C:\incubating-log4net-1.2.10\bin\sscli C:\incubating-log4net-1.2.10\bin\cli\1.0 C:\incubating-log4net-1.2.10\bin\cli\1.0\release C:\incubating-log4net-1.2.10\bin\cli\1.0\release\log4net.dll C:\incubating-log4net-1.2.10\bin\cli\1.0\release\log4net.xml C:\incubating-log4net-1.2.10\bin\mono\1.0 C:\incubating-log4net-1.2.10\bin\mono\2.0 C:\incubating-log4net-1.2.10\bin\mono\1.0\debug C:\incubating-log4net-1.2.10\bin\mono\1.0\release C:\incubating-log4net-1.2.10\bin\mono\1.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\mono\1.0\debug\log4net.dll.mdb C:\incubating-log4net-1.2.10\bin\mono\1.0\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\mono\1.0\release\log4net.dll C:\incubating-log4net-1.2.10\bin\mono\1.0\release\log4net.xml C:\incubating-log4net-1.2.10\bin\mono\2.0\debug C:\incubating-log4net-1.2.10\bin\mono\2.0\release C:\incubating-log4net-1.2.10\bin\mono\2.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\mono\2.0\debug\log4net.dll.mdb C:\incubating-log4net-1.2.10\bin\mono\2.0\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\mono\2.0\release\log4net.dll C:\incubating-log4net-1.2.10\bin\mono\2.0\release\log4net.xml C:\incubating-log4net-1.2.10\bin\net\1.0 C:\incubating-log4net-1.2.10\bin\net\1.1 C:\incubating-log4net-1.2.10\bin\net\2.0 C:\incubating-log4net-1.2.10\bin\net\1.0\debug C:\incubating-log4net-1.2.10\bin\net\1.0\release C:\incubating-log4net-1.2.10\bin\net\1.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\net\1.0\debug\log4net.pdb C:\incubating-log4net-1.2.10\bin\net\1.0\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\net\1.0\release\log4net.dll C:\incubating-log4net-1.2.10\bin\net\1.0\release\log4net.xml C:\incubating-log4net-1.2.10\bin\net\1.1\debug C:\incubating-log4net-1.2.10\bin\net\1.1\release C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.pdb C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\net\2.0\debug C:\incubating-log4net-1.2.10\bin\net\2.0\release C:\incubating-log4net-1.2.10\bin\net\2.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\net\2.0\debug\log4net.pdb C:\incubating-log4net-1.2.10\bin\net\2.0\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\net\2.0\release\log4net.dll C:\incubating-log4net-1.2.10\bin\net\2.0\release\log4net.xml C:\incubating-log4net-1.2.10\bin\netcf\1.0 C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug C:\incubating-log4net-1.2.10\bin\netcf\1.0\release C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.pdb C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\sscli\1.0 C:\incubating-log4net-1.2.10\bin\sscli\1.0\debug C:\incubating-log4net-1.2.10\bin\sscli\1.0\release C:\incubating-log4net-1.2.10\bin\sscli\1.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\sscli\1.0\debug\log4net.ildb C:\incubating-log4net-1.2.10\bin\sscli\1.0\release\log4net.dll I noticed that there weren't any files in this folder: C:\incubating-log4net-1.2.10\bin\net\1.1\release even though there are files in the other release directories. After creating a log4net.snk file and re-building, the \1.1\release\ folder had the correct (strongly signed) assembly in it. I verified this by dragging it into Reflector. I then cleared my \bin\ directory, erased the log4net.snk file, and re-ran build.cmd and noticed that there were less folders created in the bin directory the 2nd time around: C:\incubating-log4net-1.2.10\bin\net C:\incubating-log4net-1.2.10\bin\netcf C:\incubating-log4net-1.2.10\bin\net\1.1 C:\incubating-log4net-1.2.10\bin\net\1.1\debug C:\incubating-log4net-1.2.10\bin\net\1.1\release C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.pdb C:\incubating-log4net-1.2.10\bin\net\1.1\debug\log4net.xml C:\incubating-log4net-1.2.10\bin\netcf\1.0 C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug C:\incubating-log4net-1.2.10\bin\netcf\1.0\release C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.dll C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.pdb C:\incubating-log4net-1.2.10\bin\netcf\1.0\debug\log4net.xml Is that suppose to happen? --- Curt Arnold <[EMAIL PROTECTED]> wrote: > No tag for source, but did have an identified revision number > (383994) for the source in the call for vote. Is the intent to > create the tag only after the votes by the PMC and Incubator? > > MD5 checksum verified. > > Nicko's key is not present in http://www.apache.org/dist/logging/ > KEYS, but was at pgp.mit.edu, people.apache.org:~nicko/.pgpkey and > http://people.apache.org/~henkp/trust/apache.html. > > I'd like to hear from one of the other log4net committers that they > were able to reproduce the build (with the exception of timestamps et > > al). > >
