Developing/compiling Jreepad

Source code

Two ways to get the source code:

• The Jreepad downloads page links to a source code file for each release (Jreepad-*-source.tar.gz).
• To get the very latest code, grab the Jreepad SVN tree using a terminal command like this:

  svn co https://jreepad.svn.sourceforge.net/svnroot/jreepad/trunk jreepad

 

Compiling Jreepad

Compiling Jreepad is easy - from the command-line I just type

javac jreepad/JreepadViewer.java

Actually, that's not quite true, because now I use Apache Ant which is an excellent tool to help you compile projects and do various other things, nice and automatically. So instead, I type

ant

and that does everything for me (including moving files around, packaging up the source code for release, etc). Make sure you're in the directory which contains Jreepad's "build.xml" file when you do this. (Mac developers will also need the 'extra treat' mentioned below.)

Non-Mac developers

If you're compiling Jreepad on a non-Mac platform, you'll need to download a small JAR file from Apple and put it into your classpath:

AppleJavaExtensions (ZIP file, 3.6kB)

Why?

Jreepad is platform-neutral, but if you're on Mac OSX then a couple of little adjustments occur to make Jreepad fit more neatly into the OSX environment. If you're not on Mac then these adjustments simply don't happen - they should not cause any problems.

Jreepad users don't even need to have the "AppleJavaExtensions" in their systems, since if the extensions aren't found (by reflection) then Jreepad won't attempt to use them. But you do need those packages to exist if you're compiling.

An extra treat for Mac developers

The Jarbundler ant task makes it easy to create the Mac OSX application package, directly from the ant build. It even incorporates the icon files and document associations (if you're using v1.6.1 or later).

Thanks to Will Gilbert for maintaining and improving that tool.

Contributors

Jreepad was originated by Dan Stowell, and is maintained by:

• Dan Stowell
• Przemek Wiech

Thanks to the following other people (in no particular order) for contributing or suggesting code improvements:

• Jason Lawrence Justice
• Coen Schalkwijk
• Mikhail Bakhtin
• "ExileInParadise"
• Phani Kandula
• Sander Oom
• Plus various anonymous people posting comments to the project page...