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

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.

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.

ICU4J (bundle com.ibm.icu) provides advanced Unicode and Globalization support for
software applications. The full version is included in Eclipse SDK. For those that do not need that support but
need a smaller footprint for their own products, there is a subset of ICU4J, "com.ibm.icu.base" available
from the Orbit Download Page.

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.

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

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.

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:

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:

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.

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.

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.

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.

Compare with Released
to the Compare menu. Compare the selected projects with the versions referenced
in the currently loaded map files.

Replace with Released to the
Replace menu. Replace the selected projects with the versions referenced in the
currently loaded map files.

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.