• The Eclipse Repository includes all that is produced by the Eclipse Project, including the Eclipse Platform, Java development tools, and Plug-in Development Environment, Unit Tests, and even some extra items from other projects required by Eclipse (such as Equinox and a few bundles from EMF and Orbit). Please be aware that repositories have different retention policies, and restrictions on what types can be updated with what other types. See the wiki's Update Sites document for details.

• The Eclipse SDK includes the Eclipse Platform, Java development tools, and Plug-in Development Environment, including source and both user and programmer documentation. If you aren't sure which download you want... then you probably want this one. You will need a Java runtime environment (JRE) to use Eclipse (Java SE 6 or greater is recommended).

• These packages contain the Test Framework and JUnit test plugins used to run JUnit plug-in tests from the command line. See the Platform's Automated Testing wiki page for more information and setup instructions. Includes both source code and binary.

• To install the examples, download the p2 repository zip containing the examples into a directory on disk. Select Help -> Install New Software. Select Add to add a new software site. Select Archive and specify the location of the examples p2 repository zip and Okay. You will be prompted to restart Eclipse to enable the new bundles. For information on what the examples do and how to run them, look in the "Examples Guide" section of the "Platform Plug-in Developer Guide", by selecting Help Contents from the Help menu, and choosing "Platform Plug-in Developer Guide" book from the combo box.

• This p2 repository contains the Eclipse Rich Client Platform base bundles and do not contain source or programmer documentation. These downloads are meant to be used as target platforms when developing RCP applications, and are not executable, stand-alone applications.

• This p2 repository consists of the Eclipse Rich Client Platform base bundles and their source and the RCP delta pack.

• The delta pack contains all the platform specific resources from the SDK and is used for cross-platform exports of RCP applications.

• These drops contain only the Eclipse Platform with user documentation and no source and no programmer documentation. The Java development tools and Plug-in Development Environment are NOT included. You can use these drops to help you package your tool plug-ins for redistribution when you don't want to ship the entire SDK.

• These drops contain the Eclipse Platform Runtime binary with associated source and programmer documentation.

• This p2 repository contains the Java development tools bundles only, with user documentation and no source and no programmer documentation. The Eclipse platform and Plug-in development environment are NOT included. You can combine this with the Platform Runtime Binary if your tools rely on the JDT being present.

• This p2 repository contains the JDT Runtime binary with associated source and programmer documentation.

• These drops contain the standalone batch java compiler, Ant compiler adapter and associated source. The batch compiler and Ant adapter (ecj.jar) are extracted from the org.eclipse.jdt.core plug-in as a 1.2MB download. For examples of usage, please refer to this help section: JDT Plug-in Developer Guide>Programmer's Guide>JDT Core>Compiling Java code.

• This p2 repository contains the Plug-in Development Enviroment bundles only, with user documentation. The Eclipse platform and Java development tools are NOT included. You can combine this with the Platform and JDT Runtime Binary or SDK if your tools rely on the PDE being present.

• The PDE Builders are self-contained, executable PDE Build configurations that can be used to build OSGi and Eclipse-based systems. They can also be used as the basis for more sophisticated build systems that run tests, do API scans, publish builds etc.

• These drops contain the PDE Runtime Binary with associated source.

• This p2 repository contains the CVS Client plug-ins only. The Eclipse platform, Java development, and Plug-in Development Environment tools are NOT included. You can combine this with the Platform and JDT Runtime Binary or SDK if your tools rely on the CVS client being present.

• This p2 repository contains the CVS Runtime Binary with associated source.

• 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. 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 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 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.

1. Fix Copyrights. In 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. It compares the "end dates" with the last time the file was changed. It works with either Git repositories, or CVS. 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 and manually confirmed or modified. You will need to commit any changes yourself.
2. Validate Versions Match. Once turned on, in preferences, the bundle version in the MANIFEST.MF file will be compared with the artifact version in the pom.xml file. If they "mismatch", then a marker is left in problems view, so the incorrect version can be fixed before being committed for a build. Mismatched versions can cause Tycho/Maven builds to fail and it is easy to change the version on one spot and forget the other, so all committers are encourage to use and turn on this tool.

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.

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.