Eclipse Equinox, PDE, p2, applications, and products

Equinox is the OSGi Framework used by Eclipse and an ecosystem of runtime services. The Eclipse Platform 4.40 release stream is the current stable baseline in August 2026.

Equinox framework

The standalone framework lives in org.eclipse.osgi. Equinox implements OSGi Core and adds mature diagnostics, extension registry integration, launcher, application model, security history, and platform behaviors.

Extensions versus services

Eclipse extension points are declarative contributions read by the extension registry. OSGi services are dynamic runtime objects. Eclipse applications often use both. Prefer services for dynamic collaboration; use extension points where the product ecosystem defines that contract.

PDE

Plug-in Development Environment (PDE) develops bundles/plugins, features, target platforms, applications, and products. A target platform pins what the workspace compiles and resolves against. Never let “whatever is installed in my IDE” become the implicit production target.

p2

p2 is Eclipse's provisioning system. Installable Units describe capabilities, requirements, artifacts, touchpoints, and update metadata. Repositories can assemble and update products. p2 identity/version semantics interact with OSGi bundle metadata but are not identical to Maven.

Products and applications

An Eclipse application is an executable contribution. A product defines branding, launcher, configuration, features/plugins, and update behavior. Feature-based products curate installable units; bundle-based products list plugins directly.

Diagnostics

Use the OSGi console, bundle wiring, DS/component views, PDE dependency analysis, p2 director logs, state area, and error log. Avoid deleting the entire configuration/state directory before capturing evidence.

Feynman check

Equinox is the module engine; PDE builds the product; p2 installs and updates it; extension points contribute declared features; services provide live objects.