Revamped primary build to use Maven Ant tasks. Eliminated Ivy-based build,

which was used by Maven, now Maven calls into the primary build to generate its
Proguarded jar file. Retired the Retroweaved jar file after a tremendous amount
of fucking around with Retroweaver. I think it's safe to say that the number of
people showing up with a 1.4 JDK operational in their browser is epsilon close
to zero.

pom.xml

@@ -48,26 +48,17 @@
   </repositories>
 
   <dependencies>
-    <dependency>
-      <groupId>net.sf.proguard</groupId>
-      <artifactId>proguard</artifactId>
-      <version>4.4</version>
-      <scope>compile</scope>
-      <optional>true</optional>
-    </dependency>
     <dependency>
       <groupId>com.samskivert</groupId>
       <artifactId>samskivert</artifactId>
       <version>1.0</version>
       <scope>compile</scope>
-      <optional>true</optional>
     </dependency>
     <dependency>
       <groupId>commons-codec</groupId>
       <artifactId>commons-codec</artifactId>
       <version>1.4</version>
       <scope>compile</scope>
-      <optional>true</optional>
     </dependency>
     <dependency>
       <groupId>jregistrykey</groupId>
@@ -138,9 +129,11 @@
             <phase>package</phase>
             <configuration>
               <target>
-                <property name="maven.version" value="${project.version}" />
-                <ant antfile="${basedir}/build-proguard.xml">
-                  <target name="proguard" />
+                <property name="deploy.dir" value="target"/>
+                <property name="getdown.jar" value="target/getdown-${project.version}.jar"/>
+                <property name="version.suff" value="-${project.version}.jar"/>
+                <ant antfile="${basedir}/build.xml">
+                  <target name="-proguard"/>
                 </ant>
               </target>
             </configuration>