* this seems to work better when building fat jar files
* it replaced the default output jar file (without dependencies) by the fat jar file (including all dependencies)
* removed the script that replaced the default jar file by the fat jar file
* enabled the generation of the mac wrapper, since it should work
* the mac wrapper will contain all dependencies twice
* removed the maven plugin that builds the mac application launcher (configuration was still broken)
* the minecraft code uses google guava
* when executing amidst with eclipse, an exception occured from within the minecraft jar file, while using guava
* the removed maven plugin also uses guava, but another version which seems to be incompatible with the guava version used by the minecraft jar file
* the issue was caused by eclipse adding all maven dependencies to the amidst classpath, which caused the minecraft jar file to use the wrong version of guava ... I guess
* since the maven plugin has a scope of "provided", it is not included in the amidst jar file that is generated by maven
* when executing the generated amidst jar file instead of using eclipse, the issue did not occur ... this supports my guess that eclipse adds all maven dependencies to the amidst classpath
* generates windows and mac icon files using imagemagick
* generates the executables using maven plugins launch4j for windows and appbundle for mac
* renames the jar from (removes the -jar-with-dependencies suffix)
* creates a zip file from the mac app directory
* added maven-eclipse-plugin to download javadoc and sources for maven dependencies in eclipse
* extracted the jdk version to an extra property
* added the build timestamp to the jar filename and to the manifest file
Treer
Stefan Dollase