Downloads

   Each PEd4Ant release consists of three independent packages: antlibs, 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.

For older releases or a full download inventory, visit the PEd4Ant SF.net files release archive. Typical contents of a package are described in the included readme-first file.

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 release.

• v1 -beta2
  • Sun JRE 1.5-1.6
  • Ant 1.8.0-1.8.2 only (ant.apache.org/)
  • JWare AntXtras/Foundation 3.0.0 only (antxtras.sf.net/)
• v1 -beta1
  • Sun JRE 1.4
  • Ant 1.7.x only (ant.apache.org/)
  • JWare AntXtras/Foundation v2 series only (antxtras.sf.net/)

PEd4Ant’s installation is similar to any optional Ant package. The following instructions describe how to install and verify the newest PEd4Ant package in your Ant runtime environment.

1. Download, verify, and install an Ant distribution – at least version 1.8.2. PEd4Ant only uses components of the standard Ant distribution; optional tasks are not required.
   
   
2. Download, verify, and install a PEd4Ant distribution. We suggest you download the binary distribution that already includes the third-party libraries that PEd4Ant requires (this is the “_withdeps” distribution). In the remaining steps we will use <PED4ANT_DIR> to refer to the directory into which the PEd4Ant 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.
     
     
3. Update your Ant runtime environment to include the PEd4Ant jar file <PED4ANT_DIR>/lib/jw-ped4ant.jar and all required third-party jars in its classpath. You can also specify a classpath directly to the <taskdef> instruction you use to load PEd4Ant.
   
   
4. Verify the PEd4Ant 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 PEd4Ant antlib and print out its version information. If Ant is unable to locate the PEd4Ant library or its dependencies, even this simple script will fail.
   
   
5. Read the Overview page to get an idea of how to use PEd4Ant.
   
   
6. Start using PEd4Ant!

Below are the steps you must follow to use PEd4Ant after you download and expand the PEd4Ant ‘_withdeps’ (with dependencies) distribution. The examples assume you run the Ant scripts from inside the etc directory of the distribution.

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

1: <project name="ped4ant:check" basedir="." xmlns:ped="jwaresoftware.ped4ant">

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

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

Load the AntXtras and PEd4Ant antlibs into your Ant scripts using the path we defined in step 2. Note that we specify the URI of our declared “ped” namespace using the <taskdef>’s uri parameter and we load the AntXtras components into the default Ant namespace. (You don’t have to load the AntXtras antlib if you don’t need those components!)

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

Verify you can access PEd4Ant components from your Ant script. Here we use the AntXtras <vendorinfo> task to load the build information for PEd4Ant and also try to create an empty in-memory Properties object.

1: <target name="about-ped4ant">
2:   <vendorinfo name="ped4ant"/>
3:   <show message="RELEASE: ${ped4ant.build.label}"/>
4:   <ped:makeproperties under="about"/>
5: </target>

If you would like to compile the source distribution, PEd4Ant is dependent on a few other open-source offerings that you must download and install before trying to compile your own PEd4Ant binaries. If you want to compile and run PEd4Ant programmer tests you need to download the distributions that contain test support files, typically the source distributions; otherwise, the binary distributions are fine.

Main Dependencies:

• Apache’s Ant 1.8.2 (ant.apache.org/)
• JWare’s AntXtras 3.0.0 source distribution (antxtras.sf.net/)

For Programmer Tests:

• JUnit 3.8.x (junit.org/)
• A regular expression provider like Jarkarta RegExp (jakarta.apache.org/)

As Maven2 POM:

• jw-ped4ant-1.0.0.pom

You can compile the PEd4Ant sources from any Java IDE. The PEd4Ant source distribution also contains an ez-build.xml Ant script in the /etc directory that can generate the basic antlib, javadocs, and source package. You must update the ez-build.properties file with details from your environment before doing the Ant build. Read the ez-build-README file for details.