I’m writing a small program and I’m packaging it in an executable JAR file so that all the end user has to do is double-click on it to run it. None of that command-line madness that… okay, that’s another rant. ANYWAY, my particular program uses an external package that’s ALSO stored in a jar file. To put everything in one JAR means putting a jar inside another jar.
That part is easy.
Ah, but I still want my main jar file to be executable. Still easy.
AH, but I want it to run anywhere on the destination file system, without the end user having to dick mess around with CLASSPATH statements and other crap, trying to point my application to a jar file that’s contained in its own archive. Nor do I want to spend time setting CLASSPATH statements INSIDE the jar file, because a) I have more important things to do and b) they don’t work as advertised.
Fortunately, there’s a solution.
(more…)
Popularity: 19% [?]