Eclipse RCP lets you build a standalone desktop application from Eclipse’s plug-in platform, without shipping the IDE itself. For a first project, install Eclipse with the Plug-in Development Environment (PDE), create a Plug-in Project using the Hello RCP template, set an isolated target platform, run it from PDE, and create a product configuration when you are ready to export it.
What Eclipse RCP is—and how it differs from a plug-in
The Eclipse Foundation defines the Rich Client Platform as “the minimal set of plug-ins needed to build a rich client application.” Those plug-ins provide the underlying application framework, including the dynamic plug-in model, UI toolkits, and extension points. An RCP application uses that foundation while leaving out IDE-specific components it does not need. Eclipse: Building a Rich Client Platform application
A plug-in is a deployable component that contributes functionality to an Eclipse-based application. Its manifest declares its identity, version, and dependencies. An RCP application is the assembled client: it combines the platform components it needs with the application’s own plug-ins. A plug-in project can therefore be part of an RCP application, but creating a plug-in alone does not automatically create a standalone product.
What you need before creating a project
Use an Eclipse distribution that includes PDE, the Plug-in Development Environment. PDE provides project wizards, manifest editors, launchers, product editors, and export tools for plug-ins and RCP products. Its official overview describes tooling for creating, developing, testing, debugging, building, and deploying Eclipse plug-ins and RCP products. Eclipse: Plug-in Development Environment Overview
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchOpen the Plug-in Development perspective to work with PDE’s relevant views and editors. You will also need to choose a target platform: the controlled Eclipse installation or repository against which PDE resolves dependencies and runs the application.
Create and run your first RCP application
- Create the project. Select File > New > Project > Plug-in Development > Plug-in Project. In the project wizard, enable the option to create a rich client application and select a starter template such as Hello RCP. The Eclipse tutorial says the template creates the initial project and a launchable workbench. Eclipse Foundation: Rich Client Platform tutorial
- Set the target platform. Configure PDE to use the Eclipse installation or repository you intend to develop against. This keeps the development environment’s unrelated IDE plug-ins from becoming accidental dependencies of your product. Eclipse: Target platform
- Launch the application. Use the PDE launcher to run the Eclipse application and debug it while developing. PDE launchers support testing and debugging Eclipse applications and OSGi bundles. Eclipse: PDE launchers
At this point, you are running the application from your development environment. That is useful for iteration, but it is not the same as packaging a distributable application for use outside the IDE.
Rank #2
Prepare a standalone product for export
Create a product configuration when you need a deployable RCP distribution. A product configuration defines the application to assemble, its dependent plug-ins, native launcher, and branding. PDE’s product export wizard can export it to a directory or another available distribution target. Eclipse: Exporting a product
- Create or open the product configuration for your application in PDE’s product editor.
- Check that the product identifies the intended application and includes the plug-ins it depends on for the target platform.
- Set the product’s branding and native launcher options as needed.
- Run the PDE product export wizard and select a destination for the distribution.
- Test the exported product outside the development launch before distributing it.
Understand the main Eclipse RCP components
- Plug-ins and bundles: The modular units that make up the application and its platform. Their manifests describe identity, version, and dependencies.
- PDE: Eclipse’s development tooling for creating, launching, debugging, assembling, and exporting plug-ins and RCP products.
- Target platform: The selected Eclipse installation or repository used to resolve bundles and run the application. Keeping it explicit helps separate product dependencies from the IDE used to build the product.
- Product configuration: The assembly and branding definition for a standalone distribution.
- Eclipse 4 application model: The e4 approach uses dependency injection and services. Eclipse supplies E4Application as a default entry point, although an application can define its own. Eclipse: Eclipse 4 application model
Legacy 3.x-style workbench or Eclipse 4/e4?
Both approaches use Eclipse’s plug-in foundation, but they organize application composition differently. The Eclipse documentation establishes the e4 service and application model as well as the shared plug-in and extension-point foundation; it does not establish a universal migration path or declare one approach best for every project.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Area | Legacy 3.x-style workbench | Eclipse 4/e4 |
|---|---|---|
| Application configuration | Typically configures the workbench programmatically. | Uses an application model; Eclipse provides E4Application as a default entry point, with custom entry points also possible. |
| Dependency management | Uses plug-in and bundle dependencies. | Uses the same plug-in foundation and adds a service-oriented approach with dependency injection. |
| UI composition | Uses the established workbench and extension-point approach. | Uses the e4 application model alongside the Eclipse plug-in and extension-point foundation. |
| Target platform | Should be isolated to control which Eclipse components the application uses. | Should likewise be isolated; target-platform control is relevant to both approaches. |
| Product export and branding | PDE product configuration and export provide the distribution workflow. | PDE product configuration and export provide the distribution workflow. |
For further reading on the Eclipse 4.x API, the Eclipse RCP documentation lists Eclipse 4 RCP by Lars Vogel and tutorials by Lars Vogel and Jonas Helming. Eclipse RCP documentation and resources
Quick Recap
Best Value
Rank #4
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
