Top Eclipse Companies

Technical Evaluation Framework: Vetting Eclipse IDE & RCP Engineering Consultants

Eclipse Rich Client Platform (RCP) and Eclipse plugin development power specialized desktop enterprise engineering tools. Vetting specialists requires assessing OSGi modularity.

1. Eclipse RCP & Plugin Architecture

• ▸
  OSGi Modularity & Equinox: Designing modular bundles, service components, extension points, and OSGi lifecycle management.
• ▸
  SWT, JFace & UI Architecture: Building rich desktop user interfaces using Standard Widget Toolkit (SWT), JFace viewers, and custom editors.
• ▸
  Eclipse 4 (e4) Architecture: Leveraging dependency injection, the e4 application model, and modern CSS-based theme engines.

2. Buyer Diligence & Vetting Criteria

1. ▸
   Build Automation via Tycho: Automating Eclipse builds and headless product generation using Maven Tycho and p2 repositories.
2. ▸
   Cross-Platform Packaging: Building and testing native desktop installers across Windows, macOS, and Linux platforms.
3. ▸
   Legacy Eclipse 3.x to e4 Migration: Structured pathways for modernizing legacy 3.x workbench applications to modern Eclipse e4 architectures.

3. Red Flags to Watch For

• ▸
  SWT Thread Access Violations: Updating UI elements outside the SWT display thread, causing desktop UI crashes.
• ▸
  Tight Coupling Across OSGi Bundles: Violating OSGi modularity by exposing internal package implementations instead of clean service interfaces.
• ▸
  Manual Product Exporting: Relying on manual Eclipse export wizards instead of headless, automated Maven Tycho build pipelines.