Downloads ${label}

Eclipse ${release} ${buildTypeName} Build: ${label}

This page provides access to the various deliverables of Eclipse Platform build along with its logs and tests.

Reports

The Reports page provides detailed build and tests logs and analyses of various aspects of this build.

Test Results Summary

Tested Platform Failed Passed Total Runtime

Git Log

The following Git repositories changed since ${gitBaselineTag} until this build (${gitTag}):


Checksums (SHA 512) and GPG Signatures

The SHA512 checksum of each artifact is provided individually in the tables below. To verify the integrity of a downloaded artifact its checksum, computed by any suitable program (the details below provide examples), can be compared with the listed one.
The following instructions describe how to also verify a downloaded artifact's authenticity.

Obtain checksums and signature files

To verify the authenticity and integrity of any artifact provided on this page, download the SHA512 Checksums file and its GPG signature, to the same directory as the files to check. On the CLI both can be downloaded using, for example, the commands: curl -O https://download.eclipse.org/eclipse/downloads/drops4/${identifier}/eclipse-${label}-checksums
curl -O https://download.eclipse.org/eclipse/downloads/drops4/${identifier}/eclipse-${label}-checksums.asc

Verify checksums authenticity

The authenticity of the checksums file can be verified by executing the command:

gpg --verify eclipse-${label}-checksums.asc

On successful verification the output is similar to:

gpg: assuming signed data in 'eclipse-${label}-checksums'
gpg: Signature made Tue Jan 27 00:32:27 2026
gpg:                using RSA key 9E3044071B758EBCB7E45673700E4F39BC05364B
gpg: Good signature from "Eclipse Platform Project <platform-releng-dev@eclipse.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 3C91 FED3 922D 5229 6888  BAE9 B6D3 AB9B CC64 1282
     Subkey fingerprint: 9E30 4407 1B75 8EBC B7E4  5673 700E 4F39 BC05 364B

If Eclipse artifacts are verified for the first time, the displayed output will probably indicate that the public key is missing:

gpg: Can't check signature: public key not found

In this case the the public key has to be received first, for example by executing: gpg --keyserver hkps://keyserver.ubuntu.com --recv-keys 9E3044071B758EBCB7E45673700E4F39BC05364B

Verify artifact integrity

To verify that an artifact, downloaded from this page and located in the same directory as the signature file, matches the checksum recorded in the authentic checksums file, run:
  • On Linux (or Windows in a POSIX environment)
    sha512sum --check --ignore-missing eclipse-${label}-checksums The output should be similar to
    eclipse-SDK-${label}-linux-gtk-x86_64.tar.gz: OK
  • On Windows:
    certutil -hashFile <file-to-verify> SHA512 and compare the displayed checksum with the one recorded in the signed checksums file for the corresponding artifact.

Eclipse p2 Repository

Eclipse p2 Repository

The Eclipse p2 Repository includes all artifacts produced by the Eclipse Project, including the Eclipse Platform, the Equinox OSGi runtime, Java development tools, Plug-in Development Environment and even some extra items from other projects required by Eclipse (such as 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 information on the different build types at the Eclipse Downloads page for details.

To update your Eclipse installation to this development stream, you can use the software repository at
${updatesP2RepositoryComposite}

To update your build to use this specific build, you can use the software repository at
${updatesP2Repository}

Eclipse SDK

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. You will need a Java installation, ideally a JDK, to run Eclipse (Java-21 or greater is required).

Tests and Testing Framework

Tests and Testing Framework

These packages contain the Test Framework and JUnit Test Plug-ins 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.

Platform Runtime Binary

Platform Runtime Binary

These products contains 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 products as base to package your tool plug-ins for redistribution when you don't want to ship the entire SDK.

JDT Core Batch Compiler

JDT Core Batch Compiler

These archives 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 lean download. For examples of usage, please refer to the help section:
JDT Plug-in Developer Guide > Programmer's Guide > JDT Core > Compiling Java code

SWT Binary and Source

SWT Binary and Source

These archives 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 eclipse/updates/$VERSION/plugins/org.eclipse.swt.examples_*.jar. Then copy the file to C:\SWT. Now you can run the examples as described in SWT Examples. 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