These drops contain the SWT libraries and source for standalone SWT application development. For examples of standalone SWT applications refer to the snippets section of the SWT Component page.
To run a standalone SWT application, add the swt jar(s) to the classpath and add the directory/folder for the SWT JNI library to the java.library.path. For example, if you extract the download below to C:\SWT you would launch the HelloWorld application with the following command:
java -classpath C:\SWT\swt.jar;C:\MyApp\helloworld.jar -Djava.library.path=C:\SWT HelloWorld
Note that if you are running on Eclipse 3.3 or later, you do not need to specify the library path, so you would launch the HelloWorld application with the following command:
java -classpath C:\SWT\swt.jar;C:\MyApp\helloworld.jar HelloWorld
To run the standalone SWT examples that are shipped with Eclipse, download them from here. Then copy the file eclipse\plugins\org.eclipse.swt.examples_xxx\swtexamples.jar to C:\SWT. Now you can run the examples that are described here. For example:
java -classpath swt.jar;swtexamples.jar org.eclipse.swt.examples.controlexample.ControlExample
On Linux systems, note that the classpath separator character is a colon, so the equivalent command becomes:
java -classpath swt.jar:swtexamples.jar org.eclipse.swt.examples.controlexample.ControlExample
This plug-in provides features that can help committers with the Eclipse development process. It is not intended as a "tool to extend", or provide API, etc. It is a simple utility. You can install the tool from the usual Eclipse Project repositories, or the zipped repo provided on the download page. Since it uses several "internal" non-API methods, you may have to have one that "matches" the version of your development environment.
Currently, the tool provides two important functions.
Older tools for use with CVS: The following tools are for using with CVS map files, and while we have every expectation they still work fine, they are not actively used by many committers now that most have moved to use to Git, so in theory they might be less stable. If you still have a use for them, that's great, and if you find bugs, we'll accept them as valid, but will likely require a high quality patch before much effort is spent on it, since they are a low priority for the Eclipse Platform team.