package as an executable jar

[hrj]

... as per this idea.

[ghost]

I advise you to package it as a "native" software rather than as an "executable" JAR because the latter has several limitations. For example, you cannot modify the size of the Java heap by using -Xmx when the end user just double-clicks on your "executable" JAR... or you have to create 2 JVMs (one that just passes the parameters to the second one that executes your software). Moreover, some web browsers on some platforms put a JAR into a ZIP but don't modify the name of the file, the end user just obtains a broken JAR that it can't run. You can use my tool to make a self-contained native application bundle from a fat JAR: http://tuer.sourceforge.net/en/documentation/#jndt