Eclipse Rich Client Platform

Eclipse Rich Client Platform
Name	Eclipse Rich Client Platform
Developer	Eclipse Foundation
Released	2003
Latest release version	4.x
Programming language	Java
Operating system	Cross-platform
License	Eclipse Public License

Eclipse Rich Client Platform is a modular, extensible framework for building desktop applications using the Eclipse Foundation ecosystem and Java (programming language). It provides a reusable runtime, modularity through OSGi, and a rich set of UI services derived from the Eclipse IDE architecture. Developers use it to create domain-specific tools and enterprise clients leveraging the SWT and JFace toolkits within a component-oriented platform.

Overview

The platform originates in the architecture of the Eclipse integrated development environment and emphasizes modularity via OSGi bundles, UI composition via SWT, and extensibility through an Eclipse extension registry pattern. It targets desktop applications running on Microsoft Windows, macOS, and Linux, and integrates with build tools such as Apache Maven, Gradle, and automation systems like Jenkins and GitLab. Governance and ecosystem activity are coordinated by the Eclipse Foundation under the Eclipse Public License.

Architecture and Components

The core runtime relies on the Equinox OSGi implementation and the Eclipse workbench model influenced by the Model-View-Controller pattern and component models used in IBM tooling. Key components include the workbench window, perspectives, views, editors, and the extension registry that enables plugins contributed by organizations such as IBM, Intel, and Red Hat. UI components are implemented with SWT (using native widgets) and higher-level APIs in JFace. The update and provisioning mechanisms historically used p2 for provisioning, with integration into Tycho and Maven for build pipelines. Service-oriented capabilities leverage OSGi services, and integration with Eclipse Modeling Framework (EMF) and Graphical Editing Framework (GEF) enables domain-specific modeling and diagram editors. The headless runtime supports JUnit test harnesses and continuous integration in Travis CI or CircleCI environments.

Development and Deployment

Developers author features and plugins using Java (programming language), define extension points with XML manifest metadata, and assemble product configurations packaged via p2 repositories or native installers created with WiX Toolset for Microsoft Windows or pkgbuild for macOS. The development workflow commonly involves Eclipse IDE for authoring, Git for source control, continuous integration with Jenkins or GitHub Actions, and release management coordinated by teams at organizations like Red Hat and SAP SE. Packaging can target containerized environments using Docker images for distribution of backend services, and automated testing uses frameworks such as SWTBot and AssertJ Swing for UI tests. Internationalization and accessibility conform to standards promoted by organizations including W3C and ISO.

Application Examples and Use Cases

The platform has been used to build specialized tools and commercial products across industries: integrated engineering environments by Siemens, medical imaging viewers by companies working with Philips, geospatial analysis tools in collaboration with Esri, and financial trading terminals from firms leveraging modular UI frameworks. Research groups at institutions like MIT and Stanford University have built modeling environments using EMF and GMF for domain-specific languages. Open-source projects such as Apache Subversive clients, the Eclipse IDE itself, and various Eclipse Foundation projects illustrate extensible plugin ecosystems. Use cases include Integrated development environment-style toolchains, scientific visualization clients, and offline-capable enterprise dashboards deployed by organizations like Siemens and Bosch.

Comparison with Other RCP Frameworks

Compared with frameworks such as NetBeans Platform, JavaFX-based RCPs, and Qt applications developed with C++, the platform emphasizes OSGi modularity and the extension-registry model inherited from the Eclipse IDE. The NetBeans Platform offers a different module system and windowing model, while JavaFX prioritizes modern scene graph UI and styling with CSS, and Qt provides native C++ bindings and a signal-slot architecture used by projects at KDE. Commercial alternatives like IntelliJ IDEA platform are oriented toward proprietary plugin ecosystems maintained by JetBrains. Choices among these are influenced by factors such as vendor support (e.g., Red Hat, Eclipse Foundation), language preference (Java (programming language) vs C++) and integration with modeling frameworks like EMF or UML toolchains.

History and Evolution

The platform evolved from the initial design of the Eclipse IDE created with sponsorship from IBM and formalized under the Eclipse Foundation in the early 2000s. Major milestones include the stabilization of the OSGi-based Equinox runtime, the introduction of p2 provisioning, migration toward a model-based workbench in the 4.x Eclipse Foundation releases, and ongoing modernization efforts to interoperate with Maven and Gradle build ecosystems. Contributors have included companies such as IBM, Red Hat, SAP SE, and academic labs from University of California, Berkeley and TU Berlin. The platform continues to adapt alongside cloud-native initiatives and desktop virtualization trends advocated by organizations like Cloud Native Computing Foundation.

Category:Software platform