1. Introduction  
  Luntbuild is a build automation and management tool based on the popular apache ant. If you are 
  not familiar with ant, or already have a makefile or build script with no relates to ant, it does 
  not matter. There are detailed information in the user manual tells how to write a very simple ant 
  build script to wrapper your makefile or build script.
  With luntbuild, daily build, or furthur, continuous integration can be easily achieved. 
  Daily build or continuous integration is considered a best pratice during software development. 
  Refer to the following articles to learn the benefits of continuous build if you are not familiar 
  with that:
  http://www.martinfowler.com/articles/continuousIntegration.html
  http://www.joelonsoftware.com/articles/fog0000000023.html

  Roughly, luntbuild works in the way like most other build tools does:
  1) Get source code from a version control system
  2) Set a label on current source code
  3) Run a ant build script in the source tree
  4) Publish the build log and build artifacts
  
  But why choose luntbuild? Because it has the following important benefits which other tools have not all of them:
  1) It is open source and free
  2) The configuration and monitoring is simple, all from a clean web interface
  3) It is not only a build scheduling system, but also a build artifacts management system. You can easily
     navigate for history builds.
  4) It has the notion of "view". By using view, you can configure multiple modules with different
     branches or labels, and combine them together to build. 
  5) Various strategies when scheduling build, such as build strategy, label strategy, mail strategy, etc.
  6) Flexible clean and increment build management. For example, you can schedule a 
     nightly build and let it been clean build in order to achieve reliability. And you can schedule a 
     hourly build and let it been increment in order to achieve speed. 
  7) Easily manual build or rebuild of history build.
  8) It can populates build information into a property file from which
     your application can read and show information such as build number, build date, upgrade hyperlink, etc.
  9) Flexible versioning strategy which you can configure easily. 
  10) Be able to use different jdk or ant for every project/every view.
  11) 100% pure java code, run cross-platform

  The following important features are planned: 
  1) More version control system support. Currently luntbuild supports visual source safe, cvs, subversion, base clearcase,
     clearcase UCM, perforce, and starteam
  2) Add luntbuild API to easily integrate luntbuild with bug tracking tools, project management tools, 
     or automated testing tools.
  3) User authentication and authorization for accessing luntbuild.
  4) Integrate with remote ant to support build distribution and multiple-platform build.
  5) Integrates with eclipse or other IDEs to let you easily update your development environment 
     from for example latest success builds.

  And more...

2. Install and run! 
  NOTE: this procedure is intended for a clean installation, for upgrades, please refer to the release 
  notes. 
  1) Download source or binary distribution from http://www.sf.net/projects/luntbuild/

  2) Jump to step 6 if you've downloaded the binary distribution. Otherwise, 
     continue here to compile the source distribution

  3) Make sure you have jdk1.4 or jdk1.5 installed. Access http://java.sun.com/ for jdk dowloads 
     if you have not them installed.

  4) Extract the source distribution into a directory, suppose "/luntbuild-src". 
     Change to directory "/luntbuild-src/build" directory. Run build.bat on windows platform, 
     or run "sh build.sh" on unix-like platform or linux platform.
     NOTE: starteam adaptor will not get built by default. If you want to get starteam adaptor built, 
     you need to put starteam SDK jar file(starteam60.jar for starteam 6.0 for example, normally shipps 
     with a starteam client installation) and put it into "/luntbuild-src/lib" directory before build 
     the source.

  5) After build finished goto /luntbuild-src/distribute directory, you will get the binary distribution.

  6) Extract the binary distribution to a directory, suppose "/luntbuild".

  7) Make sure you have tomcat-4.1.30 or upper version installed
     Access http://jakarta.apache.org/tomcat/index.html for tomcat download 
     if you have not them installed. Suppose tomcat installed in directory "/tomcat", 
     and suppose you access tomcat at http://build-server.foobar.com

     NOTE: On windows platform, you should not start tomcat in NT service mode, it need to be run foreground.

  8) Copy /luntbuild/web/luntbuild.war to /tomcat/webapps/. Start tomcat and luntbuild.war should be automatically
     extracted as luntbuild/web/luntbuild/. 

  9) Edit the file /tomcat/webapps/luntbuild/WEB-INFO/web.xml, Change value of parameter "installDir" to the 
     installation directory for luntbuild, that is /luntbuild here. 
     
     NOTE: On unix-like platform, please make sure the tomcat process have full read/write access to the luntbuild
     installation directory

  10) Based on your version control system, install proper version control system client as demonstrated below: 

        a) If you are using visual source safe
           You should install visual source safe 6.0 software in your build machine. You can download from 
           http://download.microsoft.com. 

        b) If you are using cvs
           You should install proper cvs client based on your platform, you can download from http://www.cvshome.org or 
           http://www.cvsnt.org if you are using windows platform. Make sure the cvs executable is on the system path 

        c) If you are using subversion
           Subversion client software should be installed in your build machine, and the svn executable should be 
           on the system path. You can download subversion at http://subversion.tigris.org

        d) If you are using starteam
           Support for starteam needs the StarTeam API which is only available to licensed users of StarTeam. 
           You must have starteam-sdk.jar(or starteam60.jar for starteam6.0) put into /tomcat/webapps/luntbuild/WEB-INFO/lib.
           Normally this jar file will be avaiable as one of the runtime file after you install starteam client software. 

           IMPORTANT NOTE: For windows platform, the above step is not sufficient, you will need to have a full 
           installation of starteam SDK runtime(which will install some runtime dlls and put them into the 
           windows system path). Normally this is part of starteam client installation. 

        e) If you are using perforce
           You should have perforce client installed in the build machine, and make sure the p4 command line 
           executable exists in the system path. Contact http://www.perforce.com for any licensing information.

        f) If you are using clearcase
           You should have clearcase client installed in the build machine, and make sure the cleartool command line 
           executable exists in the system path. Also you should make sure the account to run tomcat should be able 
           to access your clearcase server and can make snapshot views.

  11) Restart tomcat, open the web browser, navigate to http://build-server.foobar.com/luntbuild/, 
      and you will get to the luntbuild page. (The first web access for luntbuild will cost some seconds, 
      please wait for some time) 

3. Support
  For any question, pls. access http://www.luntsys.com/luntbuild/ for supporting request. Also the luntbuild logs 
  under the installation directory may help to find the problem. 