Details

• Eclipse SDK
  • 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.
    Eclipse does not include a Java runtime environment (JRE). You will need a 1.4.2 level or higher Java runtime or Java development kit (JDK) installed on your machine in order to run Eclipse. Click here if you need help finding a Java runtime.
• JUnit Plugin Tests and Automated Testing Framework
  • These drops contain the framework and JUnit test plugins used to run JUnit plug-in tests from the command line. Click here for more information and installation instructions. Includes both source code and binary.
• Example Plug-ins
  • To install the examples, first make sure you have exited your Eclipse program. Then download the zip file containing the examples and extract the contents of the zip file to the same directory you used for your SDK installation. For example, if you installed the Eclipse Project SDK on d:\eclipse-sdk then extract the contents of the examples zip file to d:\eclipse-sdk. Start Eclipse. The example plug-ins will be installed. 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.
• RCP Runtime Binary
  • These drops contain the Eclipse Rich Client Platform base plug-ins 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.
• RCP SDK
  • These drops consist of the Eclipse Rich Client Platform base plug-ins and their source and the RCP delta pack. The delta pack contains all the platform specific resources from RCP and the platform and is used for cross-platform exports of RCP applications.
• com.ibm.icu.base binary and source Plug-ins
  • This plugin is a replacement plugin for the com.ibm.icu plugin. If the size of your application overrides the need to adopt ICU4J, use this plugin *in place of* the ICU4J plugin (com.ibm.icu). To install and use this plugin:
    1. Extract the zip at the root of your Eclipse install directory
    2. In the \eclipse\plugins directory, delete com.ibm.icu_<version>.jar and the directory com.ibm.icu.source_<version>
    3. In \eclipse\features\org.eclipse.rcp_<version>\feature.xml, replace the id of the com.ibm.icu plugin entry with com.ibm.icu.base.
• Platform Runtime Binary
  • 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.
• Platform SDK
  • These drops contain the Eclipse Platform Runtime binary with associated source and programmer documentation.
• JDT Runtime Binary
  • These drops contain the Java development tools plug-ins 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.
• JDT SDK
  • These drops contain the JDT Runtime binary with associated source and programmer documentation.
• JDT Core Batch Compiler
  • 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.
• Jar Processor
  • These drops contain the standalone jar processor and associated source. The jar processor is extracted from org.eclipse.update.core. For details, see the wiki pages for Update Site Optimization and Pack200 Compression.
• PDE Runtime Binary
  • These drops contain the Plug-in Development Enviroment plug-ins 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.
• PDE SDK
  • These drops contain the PDE Runtime Binary with associated source.
• CVS Client Runtime Binary
  • These drops contain 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.
• CVS Client SDK
  • These drops contain the CVS Runtime Binary with associated source.
• SWT Binary and 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 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
• org.eclipse.releng.tools plug-in
  • 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.