calling out to Ant to do the Proguard build.
Running Ant from within Maven (which then runs Maven from within Ant) no longer
works as of Maven 3.
While I was in here, I changed the build to use the Proguard-ed artifact as the
primary artifact, and changed the POM to reflect that none of the dependencies
are transitive.
page hosting the applet and the launched application through a simple server
socket bound to the loopback address on any available port (where the port
is passed to the application as a system property). Not tested yet, but it
shouldn't affect any deployments that don't specifically enable it.
getdown-pro.jar and it's only 10% larger (109k -> 121k), and it vastly
simplifies life for users.
Just use getdown-pro.jar for all of your Getdown-related needs:
- use it to install your application
- use it in your build scripts for the various Getdown tasks
- link against it in your app to use LaunchUtil or to embed Getdown
We'll even ship this on the website as simply getdown.jar. I'm tempted to ship
this in Maven and modify the main Getdown POM to not export any of its
dependencies. However, that will require a bunch of build file tweaking, which
I'd rather save for another day.
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.
annoying dependency on javaws.jar (which no longer even includes JarDiff, now
that lives in $JAVA_HOME/samples/jnlp/servlet/jardiff.jar). We had already
forked JarDiffPatcher, so this completes the circle. Now I can also directly
fix some of the annoying JarDiff bugs we were working around, which I'll do at
some point.
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.
Michael Bayne