--- a/build.xml	Thu Jun 08 18:11:12 2006 -0400
+++ b/build.xml	Tue Jan 25 17:06:57 2011 -0500
@@ -1,88 +1,23 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- You may freely edit this file. See commented blocks below for -->
-<!-- some examples of how to customize the build. -->
-<!-- (If you delete it and reopen the project it will be recreated.) -->
-<project name="html2wiki" default="default" basedir=".">
+<project name="html2wiki" default="default" basedir="."
+    xmlns:ivy="antlib:fr.jayasoft.ivy.ant"
+    xmlns:ssdt="http://www.ssdt-ohio.org/ant/common">
     <description>Builds, tests, and runs the project html2wiki.</description>
     <import file="nbproject/build-impl.xml"/>
     
-    <property name="project.name"    value="html2wiki" />
-    <property name="project.version" value="0.1-0" />
-
-    <property file="../../build.global"/>    
-    <property name="ssdt.home.dir" value="../../"/>
-    <property name="tools.dir" value="${ssdt.home.dir}/Tools"/>    
-    <import file="${tools.dir}/jalopy/ant/jalopy-ant.xml" optional="true"/>
-    <import file="${tools.dir}/checkstyle/ant/checkstyle-ant.xml"/>
-    
-        <import file="${tools.dir}/findbugs/ant/findbugs-ant.xml"/>
-    <!--
-
-    There exist several targets which are by default empty and which can be 
-    used for execution of your tasks. These targets are usually executed 
-    before and after some main targets. They are: 
-
-      -pre-init:                 called before initialization of project properties
-      -post-init:                called after initialization of project properties
-      -pre-compile:              called before javac compilation
-      -post-compile:             called after javac compilation
-      -pre-compile-single:       called before javac compilation of single file
-      -post-compile-single:      called after javac compilation of single file
-      -pre-compile-test:         called before javac compilation of JUnit tests
-      -post-compile-test:        called after javac compilation of JUnit tests
-      -pre-compile-test-single:  called before javac compilation of single JUnit test
-      -post-compile-test-single: called after javac compilation of single JUunit test
-      -pre-jar:                  called before JAR building
-      -post-jar:                 called after JAR building
-      -post-clean:               called after cleaning build products
-
-    (Targets beginning with '-' are not intended to be called on their own.)
-
-    Example of inserting an obfuscator after compilation could look like this:
+    <property file="../build.global"/>
+    <property file="../../build.global"/>
 
-        <target name="-post-compile">
-            <obfuscate>
-                <fileset dir="${build.classes.dir}"/>
-            </obfuscate>
-        </target>
-
-    For list of available properties check the imported 
-    nbproject/build-impl.xml file. 
-
-
-    Another way to customize the build is by overriding existing main targets.
-    The targets of interest are: 
+    <property name="ssdt.devel.kit" value="${user.home}/.ssdt"/>
+    <property name="ssdt.devel.kit.src" value="http://hg.ssdt-ohio.org/browse/public/develkit"/>
+    <mkdir dir="${ssdt.devel.kit}"/>
+    <get dest="${ssdt.devel.kit}/bootstrap.xml"
+         src="${ssdt.devel.kit.src}/bootstrap.xml" usetimestamp="true" ignoreerrors="true"/>
+    <import file="${ssdt.devel.kit}/bootstrap.xml"/>
 
-      -init-macrodef-javac:     defines macro for javac compilation
-      -init-macrodef-junit:     defines macro for junit execution
-      -init-macrodef-debug:     defines macro for class debugging
-      -init-macrodef-java:      defines macro for class execution
-      -do-jar-with-manifest:    JAR building (if you are using a manifest)
-      -do-jar-without-manifest: JAR building (if you are not using a manifest)
-      run:                      execution of project 
-      -javadoc-build:           Javadoc generation
-      test-report:              JUnit report generation
-
-    An example of overriding the target for project execution could look like this:
+    <ssdt:require-ant   file="ivy-ant.xml"/>
+    <import             file="${ssdt.devel.kit}/ivy-ant.xml"/>
 
-        <target name="run" depends="html2wiki-impl.jar">
-            <exec dir="bin" executable="launcher.exe">
-                <arg file="${dist.jar}"/>
-            </exec>
-        </target>
-
-    Notice that the overridden target depends on the jar target and not only on 
-    the compile target as the regular run target does. Again, for a list of available 
-    properties which you can use, check the target you are overriding in the
-    nbproject/build-impl.xml file. 
-
-    -->
-    <target name="-pre-compile-single">
-        <antcall target="jalopy-single"/>
-    </target>
-    
-    <target name="checkstyle" depends="compile,do-checkstyle"/>
-    <target name="findbugs" depends="compile,-do-findbugs"/>
-    <target name="findbugs-view" depends="compile,-do-findbugsViewer"/>
+    <target name="-ivy-retrieve"        depends="-ivy-define, -ant-contrib-define, -lib-path-init, -ivy-retrieve-custom"/>
 
 </project>