The following people and tools were very helpful for the development of Jomic:
UnRarX, which includes the command line port of unrar Jomic uses to extract *.cbr comic archives.
pdfbox, which provides the means to parse PDF comics.
MRJ Adapter, which makes it easier for Java applications to behave like nice Mac OS X applications while retaining portability
IzPack, an installer generator for Java applications.
John Munsch for nagging about the lack of a Web Start release and posting code how to do it.
Thomas Kutschera for creating the Jomic icon.
Log4j, which logs internal messages and simplifies tracking problems both for users and developers.
Several tools that help to assure quality:
Emma analyzes code coverage of the test programs.
CheckStyle , JDepend, and FindBugs analyze the source code and help detecting problems early on.
JRefactory's pretty printer ensures consistent formating of the source code
Abbot provides a framework and a script editor for UI testing.
JUnit simplifies writting test cases.
Creation of the documentation was supported by:
The DocBook open repository features transformations to convert the documentation to HTML, JavaHelp, PDF, and some other formats.
The official DocBook homepage has all the documentation and tutorials you need to write manuals in this format.
Tidy has the monopoly on being the only XML parser in the world producing human readable error messages - at least sometimes.
Sun and Apple to give us Java Advanced Imaging for Mac OS X. While Jomic uses only a fraction of the functionality, familiarizing myself with this API was the major motivation for starting the whole thing (Well, and maybe the fact that I could not find a working comic book viewer for Mac OS X.)
Sven Van Caekenberghe for his paper on "Tuning Java Swing applications for Mac OS X", and the related example code. This saved me an awful lot of time.