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:

cd C:\SWT
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 will help with the Eclipse development process. Installing the plug-in will add the following actions. To install simply unzip the file into your plugins directory and restart Eclipse. Please use the Release feature of this plug-in to do your build submissions.

1. Release to the Team menu. This action will Tag selected projects with the specified version and update the appropriate loaded *.map files with the version. The user must have the *.map files loaded in their workspace and the use must commit the map file changes to the repository when done.
2. Load Map Projects to the Team menu. Select one or more *.map file and this action will load the projects listed in the *.map file into your workspace. Naturally the versions specified in the *.map file will be loaded.
3. Tag Map Projects to the Team menu. Select one or more *Map files and this action will tag the projects listed in the *Map files with a tag you specify.
4. Compare with Released to the Compare menu. Compare the selected projects with the versions referenced in the currently loaded map files.
5. Replace with Released to the Replace menu. Replace the selected projects with the versions referenced in the currently loaded map files.
6. Fix Copyright to the Resource Perspective Projects context menu. Select one or more projects in the Resource Perspective. This action will sanity check the copyright notices in all the *.java and *.properties files. Copyrights will be updated automatically where the tool deems appropriate. A copyright.log file will be written to the workspace directory noting odd conflicts that need to be looked at. You need to commit the changes yourself. This is the tool that was used to do the 2.1 Copyright pass.