Skip to main content

Eclipse Tycho

Eclipse Tycho is a build toolchain (build automation) that integrates Apache Maven with Eclipse OSGi, Eclipse plug-in, and RCP development to produce Eclipse-based artifacts using standard Maven workflows.

  • Builds Eclipse plug-ins, features, and update sites using Maven (build automation)
  • Supports OSGi bundle development aligned with Eclipse and Equinox conventions (OSGi application development)
  • Generates Eclipse RCP applications and products from Maven projects (desktop application packaging)
  • Reuses Maven dependency management, lifecycle, and plug-in mechanisms for Eclipse artifacts (software supply chain and dependency management)
  • Integrates with the broader Eclipse and Maven ecosystems for consistent project builds (developer tooling integration)

More About Eclipse Tycho

Eclipse Tycho is a build toolchain that connects the Apache Maven (build automation) ecosystem with Eclipse Plug-in Development Environment (PDE), OSGi (modular application platform), and Eclipse Rich Client Platform (RCP) application development. It enables organizations to build Eclipse plug-ins, features, OSGi bundles, and Eclipse products using standard Maven lifecycles and project structures while respecting Eclipse and OSGi metadata and dependency rules.

The project focuses on the problem that traditional Maven builds do not natively understand Eclipse-specific concepts such as bundle manifests, features, p2 repositories, and target platforms. Tycho provides Maven plug-ins and extensions (build automation) that interpret Eclipse metadata, resolve dependencies using p2 repositories, and produce Eclipse-compliant artifacts. This allows build engineers and developers to apply Maven-based Continuous Integration (CI), dependency management, and reproducible build practices to Eclipse-based codebases.

Core capabilities include building OSGi bundles from Eclipse plug-in projects (OSGi application development), assembling Eclipse features and products (application packaging), and creating p2 update sites and repositories (software distribution). Tycho reads Eclipse MANIFEST.MF, feature.xml, product configuration files, and target platform definitions to determine dependencies and build outputs. It uses the Maven lifecycle phases while delegating resolution and packaging logic to Tycho-specific plug-ins tailored for Eclipse technologies.

In enterprise environments, Tycho is used to standardize builds for Eclipse RCP applications, internal Eclipse tools, and OSGi-based services that follow Eclipse conventions (enterprise application tooling). Teams can manage Eclipse artifacts alongside non-Eclipse components within a single Maven-based build, which supports consistent versioning, dependency resolution, and integration into Continuous Integration and Continuous Deployment (CI/CD) pipelines. Organizations that rely on Eclipse-based Immutable Deployment Environment (IDE) extensions or domain-specific tools can use Tycho to maintain automated builds, p2 repositories, and update mechanisms.

Tycho operates within the Eclipse Foundation governance model (open-source foundation) and aligns with Eclipse platform and Equinox runtimes, p2 provisioning system, and Eclipse Power Distribution Efficiency (PDE) project structures. It interoperates with existing Maven infrastructure such as build servers, artifact repositories, and Maven plug-ins, while introducing p2-based dependency resolution for Eclipse bundles. This positions Eclipse Tycho in a technical directory as a specialized build automation tool for Eclipse and OSGi ecosystems, bridging Maven-centric software supply chains with Eclipse-centric plug-in and RCP development workflows.