This is actually the JSPWiki build file. If you want to have the most recent version, you can get the source package.

If you are using a similar structure in your own project, you should be able to just take this file and change some values of some of the properties in the beginning of the file.

    Copyright (C) Janne Jalkanen 2001.

    Permission to use and copy freely is granted.

    This is the Ant build file for the JSPWiki project.

    The verbosity in this file is intentional - it is also
    an example for those who don't know Ant yet that well
    and would like to learn it.

    The build file assumes the following directory structure:

    |   |___[ and other misc files]
    |   |___webdocs
    |   |   |___[all .jsp files]
    |   |   |___WEB-INF
    |   |       |___web.xml [the deployment file]
    |   |       
    |   |___com 
    |       |___[...and the rest of the source code files]
            |___[...and the rest of the test source code]
    $Id: SampleAntBuildFile.txt,v 1.7 2004/10/02 06:27:51 root Exp $
    First, we define the project.  We assign it a name,
    and the default action if no action is specified on the
    command line.  Also, all relative directory references
    in the rest of the project file should be calculated from
    the current directory.
<project name="JSPWiki" default="compile" basedir=".">
  <!-- This denotes the directory where the source code lies. -->
  <property name="code.src" value="src" />
  <!-- The class files are actually put in this directory.  It is
       a good habit to keep .class -files separate from the .java -files. -->
  <property name="" value ="build" />
  <!-- Define a temporary directory, based on the system temporary directory,
       the user name, and the project name (defined above) -->
  <property name="tmpdir" value="${}/${}/${}" />

  <!-- The following three properties define the location of the
       test sources, the location of the test .class files and the
       directory where the test results are written in. -->

  <property name="tests.src" value="tests" />
  <property name="" value="tests/build" />
  <property name="tests.reports" value="tests/reports" />

  <!-- The temporary installation directory where all war-files 
       are collected, for example -->
  <property name="install.fulldir" value="${tmpdir}/install" />

  <!-- The directory where the CVS sources are checked out. -->
  <property name="install.src" value="${tmpdir}/cvssrc" />

  <!-- Define the CVS properties.  These are used when building the
       source distribution.  Normally, you shouldn't have to care about these. 
  <property name="cvs.root" value="" />
  <property name="cvs.module" value="JSPWiki" />
  <property name="cvs.tag" value="HEAD" />

  <!-- And finally, the directory where the final .zip-file is put -->
  <property name="release.dir" value="releases" />

  <!-- The base path for compilation.  We include, of course, the
       already built files in the build-directory, and then we
       add all the jar files in the "lib" -directory. -->
  <path id="path.base">
     <pathelement path="${}" />
     <fileset dir="lib">
        <include name="*.jar" />

  <!-- The path used for running tests.  We add the tests/etc directory
       to the base path defined above, since we put all the relevant
       .properties-files in tests/etc. -->
  <path id="path.tests">
      <pathelement path="${tests.src}/etc" />
      <path refid="path.base" />

  <!-- ============================================================== -->

  <!-- Initialising, cleaning, etc. -->

  <target name="init" 
          description="Initializes everything, creates directories, etc.">
     <mkdir dir="${}" />
     <mkdir dir="${}" />
     <mkdir dir="${tests.reports}" />

  <!-- Removes the build directory and the tests build directory -->
  <target name="clean"
          description="Cleans away all generated files.">
    <delete dir="${}" />
    <delete dir="${}" />

  <!-- ============================================================== -->

  <!-- Compilation targets -->

  <!-- In English this means that the "init" -target must be executed
       first.  After this, the java compiler is invoked with options
       that compile every .java file in ${code.src} into .class files
       in directory ${}.  The is no debugging information
       and the compiler is instructed to optimize the resulting code.

       For the classpath we use the previously defined path called
       "path.base" -->

  <target name="compile" depends="init"
          description="Builds the source code.">
    <javac srcdir="${code.src}"
      <classpath refid="path.base" />

  <!-- This is similar to above.  We use this to compile the
       tests. -->
  <target name="compiletests" depends="init"
          description="Builds the test code.">
    <javac srcdir="${tests.src}"
      <classpath refid="path.base" />

  <!-- ============================================================== -->

  <!--  Installation targets -->

  <!-- This target makes sure all the necessary directories exist
       for building the installation package. -->
  <target name="installinit">
    <mkdir dir="${install.fulldir}" />
    <delete dir="${install.src}" />    
    <mkdir dir="${install.src}" />
    <mkdir dir="${release.dir}" />

  <!--  Builds a Web Archive - basically a JAR file which
        also contains all of the JSP pages and can be deployed
        The archive gets put in the ${install.fulldir}.  The 
        reason for this is that this is just a temporary
        step when building the entire distribution archive.

        We include the following things:

        1) All .jar -files in the lib-directory.
        2) All .class-files from the build-directory
        3) Everything from the src/webdocs -directory
        4) Everything from the etc-directory go to the WEB-INF -directory
           of the WAR-file.

  <target name="war" depends="compile,installinit"
          description="Builds the WAR file for installation.">

    <war warfile="${install.fulldir}/${}.war"
       <lib dir="lib" includes="*.jar" />
       <classes dir="${}" includes="**/*.class" />
       <fileset dir="${code.src}/webdocs" includes="**" />
       <webinf dir="etc" includes="**" />


       Here goes some nice Ant magic...  We build the source
       code archive by directly exporting all code from the CVS
       repository, and then zipping it to the temporary installation

       Note that you must have your CVS set up so that it does
       not ask for a password when you're checking it out.

       If you don't have CVS access, you can't build a source 
       zip with this.  Sorry.
  <target name="srczip" depends="installinit"
          description="Builds source zip.">

    <cvs cvsRoot="${cvs.root}" 
         tag="${cvs.tag}" />

    <zip zipfile="${install.fulldir}/${}"
         basedir="${install.src}" />


  <!-- Builds the entire distribution set.

       We build both the WAR-file and the source zip, then
       copy in some useful files and zip the whole thing
       into the release directory.

       Note that if you don't have CVS access set up, you 
       probably can't run this.
  <target name="dist" depends="war,srczip"
          description="Builds the entire distribution archive.">
     <copy file="README" todir="${install.fulldir}" />
     <copy file="ChangeLog" todir="${install.fulldir}" />
     <copy file="doc/LICENSE" todir="${install.fulldir}" />
     <zip zipfile="${release.dir}/${}.zip"
          basedir="${install.fulldir}" />

  <!-- ============================================================== -->

  <!-- Running tests -->

  <!-- This target runs the JUnit tests that are available
       under tests/.  It generates the test result files
       into the ${tests.reports} -directory, one file per
       each tested class.  The tests are generated in
       plain text, but you can easily get XML format results
       as well, just by setting the formatter, below.

       Only tests that end with "*" are included.
       This is because then you can also use a manual
       "" in each directory, as per the JUnit

       This runs the tests in text mode.  If you want the
       pretty GUI you probably want to write a new target.
  <target name="tests" depends="compile,compiletests"
          description="Runs the JUnit tests.">

    <junit printsummary="yes" haltonfailure="no" fork="no">
           <path refid="path.tests" />
           <pathelement path="${}" />
           <pathelement path="${java.class.path}" />

        <formatter type="plain" />

        <batchtest todir="${tests.reports}">
           <fileset dir="${tests.src}">
                <include name="**/*" />
                <exclude name="**/AllTest*java" />



Add new attachment

Only authorized users are allowed to upload new attachments.
« This page (revision-7) was last changed on 02-Mar-2005 01:03 by FosterSchucker