From 1b543ab2d7309deb5526c44e772002ccfb8f5dfa Mon Sep 17 00:00:00 2001
From: Charlie Groves <charlie@threerings.net>
Date: Mon, 28 Jan 2008 22:25:20 +0000
Subject: [PATCH] 1. proguard renames classes a-z and then switches to caps
 after the first 26 2. getdown uses 30 classes from samskivert.util 3. Macs
 have case-preserving, case-insensitive filesystems 4. getdown unpacks its
 proguarded jar to combine it with the retroweaver runtime

With these 4 conditions in place, getdown-retro-pro will bafflingly lack
certain classes.  Using the update attribute on ant's jar task allows the
runtime to be inserted without proguarded files touching the filesystem, and I
can start regrowing my hair.
---
 build.xml | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/build.xml b/build.xml
index 1c8953f..a3dcb5e 100644
--- a/build.xml
+++ b/build.xml
@@ -122,12 +122,10 @@
     <weave inputjar="${basedir}/${deploy.dir}/${app.name}-pro.jar"
            outputjar="${basedir}/${deploy.dir}/${app.name}-retro-pro.jar"/>
     <!-- now combine the retroweaved jar file with the retroweaver runtime -->
-    <unjar src="${deploy.dir}/${app.name}-retro-pro.jar"
-           dest="${deploy.dir}/rptmp"/>
     <unjar src="${deploy.dir}/lib/retroweaver-rt-1.2.2.jar"
            dest="${deploy.dir}/rptmp"/>
     <jar destfile="${deploy.dir}/${app.name}-retro-pro.jar"
-         manifest="lib/manifest.mf" basedir="${deploy.dir}/rptmp"/>
+         manifest="lib/manifest.mf" basedir="${deploy.dir}/rptmp" update="true"/>
     <delete dir="${deploy.dir}/rptmp"/>
   </target>