Downloads

   Each Svn4Ant series consists of three distribution packages: binaries, documents, and source. Every package has an associated hash value and a GPG-generated signature so you can verify its integrity. To authenticate a package with any PGP or GnuPG application, download our KEYS file and import it into your public keyring.

You should use the newest Svn4Ant v2 or v3 series if possible. For older releases or a full download inventory, visit the Svn4Ant SF.net files release archive. Typical contents of a package are described in the included readme-first file. Read the Svn4Ant Future Plans section to learn the differences between the v1, v2, and v3 series.

Note that except for the JRE and Ant applications, all required third-party libraries are included as part of the “_withdeps” package for a particular series.

• v3 series:
  • Sun JRE 1.5-1.6
  • Ant 1.8.0 only (ant.apache.org)
  • JWare AntXtras/Foundation 3.0.0b1 only (antxtras.sf.net/)
  • SVNKit 1.3.2 (svnkit.com/)
• v2 series:
  • Sun JRE 1.4-1.5
  • Ant 1.7.x only (ant.apache.org)
  • JWare AntXtras/Foundation 2.0.0-2.0.1 only (antxtras.sf.net/)
  • SVNKit 1.1.6-1.1.8 only (svnkit.com/)
  • A regular expression provider supported by Ant! (Ant regular expressions)

Svn4Ant’s installation is similar to any optional Ant package. The following instructions describe how to install and verify Svn4Ant v2 or v3 in your Ant runtime environment.

1. Download, verify, and install an Ant distribution— version 1.7.1[v2] or 1.8.0[v3]. Svn4Ant only uses components of the standard Ant distribution; optional tasks are not required.
   
   
2. Download, verify, and install a Svn4Ant distribution. We suggest you download the binary distribution that contains the third-party libraries Svn4Ant requires (this is the “_withdeps” distribution). In the remaining steps we will use <SVN4ANT_DIR> to refer to the directory into which the Svn4Ant distribution was extracted or built.
   • If you must manually generate all binaries for your environment, download the source-only distribution. Be sure you also download the required third-party libraries. You must use JDK version 1.5 or later to compile the sources.
     
     
3. Update your Ant runtime environment to include the Svn4Ant jar file <SVN4ANT_DIR>/lib/jw-svn4ant.jar and all required third-party jars in its classpath. There are several ways of telling Ant about third-party jar files; the easiest method is to copy the files into your Ant distribution’s lib directory. You can also specify a classpath directly to the <taskdef> instruction you use to load Svn4Ant.
   
   
4. Verify the Svn4Ant tasks are accessible from Ant. The easiest way to do this is to run Ant against this starter script. This Ant script doesn’t actually do anything except load the Svn4Ant antlib and print out its version information. If Ant is unable to locate the Svn4Ant client library or its dependencies, even this simple script will fail.
   
   
5. Read the Overview page to get an idea of what Svn4Ant can do for you. Read the tutorial section for step-by-step instructions for using the most common client commands like checkout, update, and commit. Download the “JWare/AntXtras Svn4Ant User Guide”(pdf) as an offline reference for every Svn4Ant component.
   
   
6. Start using Svn4Ant!

Below are the steps you must follow to use Svn4Ant after you download and expand the Svn4Ant ‘_withdeps’ (with dependencies) distribution. If you downloaded the plain binary distribution (no dependencies), you must adjust the first step below to include your locations of the required third-party jar files.

Define where you’ve installed Svn4Ant using Ant’s <path> components. In this snippet we assume ‘${root.d}’ is where you have installed the Svn4Ant distribution.

 1: <dirname property="root.d" file="${basedir}"/>
 2: <path id="jware.path">
 3:   <fileset dir="${root.d}/dep">
 4:     <include name="*/lib/*.jar"/>
 5:   </fileset>
 6:   <fileset dir="${root.d}/lib">
 7:     <include name="jw-svn4ant.jar"/>
 8:   </fileset>
 9: </path>

You will need to adjust lines 3, 4, and 5 if you’ve downloaded the Svn4Ant dependencies as separate packages. Update these lines to point to wherever those packages are installed.

Define the namespace prefix for the Svn4Ant client antlib as part of your main script’s root <project> XML element. By default, we use the “svn:” prefix to refer to Svn4Ant client components under the “jwaresoftware.svn4ant.client” namespace.

1: <project name="svn4ant:checkinstall" basedir="." default="about-svn4ant"
2:          xmlns:svn="jwaresoftware.svn4ant.client">

Load the Svn4Ant client component antlib into your Ant scripts using the paths previously defined in step 1. Note that we specify the URI of our declared “svn” namespace using the <taskdef>’s uri parameter.

1: <taskdef uri="jwaresoftware.svn4ant.client"
2:       resource="org/jwaresoftware/svn4ant/client/antlib.xml"
3:       classpathref="jware.path"/>

Because Svn4Ant includes the full AntXtras/Foundation antlib, you can also load that package into your Ant scripts to get access to all of those components. We will load the AntXtras antlib before loading the Svn4Ant antlib then reuse the class loader that uses our custom class path.

1: <taskdef uri="jwaresoftware.antxtras"
2:       resource="org/jwaresoftware/antxtras/install/antlib.xml"
3:       classpathref="jware.path"
4:       loaderref="jware.classloader"/>
5:
6: <taskdef uri="jwaresoftware.svn4ant.client"
7:       resource="org/jwaresoftware/svn4ant/install/antlib.xml"
8:       loaderref="jware.classloader"/>

Verify you can access Svn4Ant client components from your Ant script.

1: <target name="about-svn4ant">
2:   <svn:libcheck/>
3:   <echo message=" SVNKit: ${svnkit.label}"/>
4:   <echo message="Svn4Ant: ${svn4ant.label}"/>
5: </target>

If you’re also going to use the plain AntXtras components, verify that you can use those items as well as the Svn4Ant items from your Ant script. Assume we have updated step 2 to declare the “oja:” prefix to refer to AntXtras components under the “jwaresoftware.antxtras” namespace URI.

1: <target name="about-svn4ant">
2:   <oja:vendorinfo name="antxtras"/>
3:   <echo message="AntXtras: ${antxtras.build.label}"/>
4:   <svn:libcheck/>
5:   <echo message="  SVNKit: ${svnkit.label}"/>
6:   <echo message=" Svn4Ant: ${svn4ant.label}"/>
7: </target>

If you would like to compile the source distribution, Svn4Ant is dependent on a few other open-source offerings that you must download and install before trying to compile your own Svn4Ant binaries. These dependencies are listed below.

Main Dependencies:

• v3 series:
  • Apache’s Ant 1.8.0 source distribution (ant.apache.org/)
  • TMate’s SVNKit 1.3.2 (svnkit.com/)
  • JWare’s AntXtras 3.0.0b1 source distribution (antxtras.sf.net/)
• v2 series:
  • Apache’s Ant 1.7.1 source distribution (ant.apache.org/)
  • TMate’s SVNKit 1.1.8 (svnkit.com/)
  • JWare’s AntXtras 2.0.1 source distribution (antxtras.sf.net/)

For Programmer Tests:

• JUnit 3.8.3 (junit.org/)
• v2 series: A regular expression provider like Jakarta RegExp (jakarta.apache.org/regexp/)

As Maven2 POM:

• v3 series: jw-svn4ant-3.0.0b1.pom
• v2 series: jw-svn4ant-2.0.0.pom