>
> BUILD SUCCESSFUL
> Total time: 3 minutes 30 seconds
>
> So, once I knew which jar was missing, I tracked it back to the gluegen build, which was failing due to the native compile, as per extra console output above... ;)  The clue was jni.h error.  Strange that after the first build this was not stopping the build (ie the gluegen fattiness or properties location made no difference in the end)
>
> So it turns out that the latest and greatest Apple updates try to put another nail in Java's coffin by reorganizing the java install.  Apple Radar #8421130.  Even after installing the recommended 'Java developer package' the jni.h was still not being picked up.  I tracked this down to 2 places in the build scripts where I had to change from:
>
> /System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Headers
> to:
> /System/Library/Frameworks/JavaVM.framework/Headers
>
> I don't know if that is the definitive fix, but at least you can add this to the 'How to build' since you might  have to support both locations for a while and it is probably going to trip more people up when they update OSX / Java.
>
> well it was nice to visit my old friend ant at least :)