WebObjects 4: Using Jikes With WebObjects on Windows NT

There are two ways to use Jikes with WebObjects and Project Builder. The first and simplest way is to replace the default Java compiler. Simply:

• Rename the existing compiler binary, javac.exe, and move it to a directory not in your system's classpath
• Rename the Jikes compiler to javac.exe, and move it to a directory in your system's classpath

The Hard Way

A better way to integrate Jikes into your environment is to integrate Jikes into Project Builder as an alternate compiler. To do this, you'll need to:

• Download the jikesSpec.plist and jikes.bat files from Apple's FTP servers
• Make sure jikes.exe and jikes.bat are in your system path
• Edit the Executables statement in jikesSpec.plist, replacing "e:/usr/local/bin/jikes.bat" with the path to your jikes.bat file
• Copy the jikesSpec.plist file into $NEXT_ROOT/Developer/Makefiles/Resources/jikesSpec.plist
• Restart ProjectBuilder

Project Builder should now display "IBM Jikes" as an option in the Project Build Attributes inspector's "compiler" popup. With this method, errors will be more likely to be properly highlighted in the build panel. The jikes.bat file simply runs the jikes compiler with the +E flag, which causes error messages to come out on a single line, allowing ProjectBuilder to pick out the filename and line number correctly in most cases. The jikesSpec.plist file is similar to the javaSpec.plist file, with additions for the different warning and error formats. This file only allows the use of Jikes on Windows NT. For more information on customizing Spec.plist files, see the documentation under $NEXT_ROOT/Developer/Makefiles/Resources/compilers.readme

Disclaimer

Whichever way you use to integrate Jikes, remember that Apple has not tested and will not guarantee or provide support for it; follow these instructions at your own risk.