Configuring Eclipse =================== This document describes how to setup Eclipse with AppleCommander. It describes configurations for Windows with Eclipse 3.3 or Mac with Eclipse 3.2. Configurations for other environments should be similar. SWT_JAR Classpath Variable ========================== When developing in Eclipse, the SWT library needs to be available. AppleCommander has been configured to expect an SWT_JAR environment variable. On Windows, go to Window -> Preferences -> Java -> Classpath Variables. Click on New button and enter SWT_JAR for the variable name. Choose the File button to set the path and locate the swt.jar. A similarly named file will be located at: /plugins/org.eclipse.swt.win32.win32.x86_3.3.0.v3346.jar On Mac, go to Eclipse -> Preferences -> Java -> Classpath Variables to add a new variable. The corresponding library will look like this: /plugins/plugins/org.eclipse.swt_3.2.2.v3236b.jar Click OK and close out of each dialog. Answer YES to the prompt regarding recompiling your entire workspace. Running AppleCommander within Eclipse ===================================== On Windows, the DLL file associated with SWT needs to be located by the JVM. To do this, add the following flag to VM arguments: -Djava.library.path="\plugins\org.eclipse.swt.win32_2.0.2\os\win32\x86" On Mac, the corresponding library is nearby; it can be added to the build as a Classpath Variable (e.g. MAC_JAR, below): /plugins/org.eclipse.swt.carbon.macosx_3.2.2.v3236.jar Java Build Path =============== The Java path build path may be edited by selecting Project -> Properties -> Java Build Path. Also, look at the Java Build Path help page. A typical .classpath might look like this: On Windows: On Mac: