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



git-svn-id: a68a83646e9f3f8749d8366215f39ba5d386d793@248 a0402a4a-d63b-ad04-3ffe-6d551d543dc1

makkus/getdown,makkus/getdown