So far, I looked over the specfile and noticed:

- That jar was using compression. So i switched-compressiong by using the jar -0 option. The performance of the gui seems to be much more robust. The rpm package is also smaller. 1.6MB instead of 1.9MB. I'm guessing this is due to bzip2 being able to compress those jar files better instead of the zipped jars.

- gui/build.xml had the debug option set to "on". set to "off" to ensure that optimizations would work.

Any other idea? I did notice the pre-compiled .dll files with the gui/bin so I don't think there's much I can do with that, unless there is source to those also.