eclipse-platform mit Homebrew Cask installieren

Projektlinks

• Homepage
• Paketmanager-Seite

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Projektgeschichte

Eclipse evolved from IBM and Object Technology International's earlier VisualAge development environments. IBM published the Eclipse Platform and Java Development Tools source on 7 November 2001 and helped establish the original Eclipse.org consortium.

The Eclipse Foundation was created in 2004 as an independent, vendor-neutral steward. The Platform continued as the common workbench, resource model, debugger infrastructure, SWT/JFace user-interface stack, OSGi runtime, and plug-in integration layer underlying Eclipse IDE distributions and rich-client applications.

Adoptionsgeschichte

Eclipse grew from a Java IDE into a general-purpose integration and rich-client platform. Its plug-in architecture was adopted both by open-source projects and commercial vendors, while the SDK remained the reference distribution for building and testing platform extensions.

The Eclipse Foundation reported that Eclipse became a major Java development and application-lifecycle-management platform and a widely used base for commercial products. Regular coordinated releases reinforced its role in downstream IDE and tooling ecosystems.

Wie es verwendet wird

Developers use the SDK to build, run, debug, and package Eclipse plug-ins, IDE extensions, and rich-client applications. Runtime behavior can be controlled through launcher options, `eclipse.ini`, `configuration/config.ini`, workspaces, and p2-managed plug-ins.

Warum Paket-Nerds sich dafür interessieren

The SDK exposes the layer beneath the audience-specific Eclipse IDE packages. It matters to package maintainers because SWT native fragments, OSGi bundles, p2 metadata, configuration areas, workspaces, and plug-in dependency resolution all have to align across operating systems and architectures.

Its architecture helped popularize large desktop applications assembled from versioned plug-ins rather than delivered as a single monolith.

Zeitleiste

• 2001: IBM published the Eclipse Platform and JDT source, and the Eclipse.org consortium was formed.
• 2004: The Eclipse Foundation was established as an independent steward.
• 2006: Eclipse reported a broad ecosystem of Eclipse-based products and millions of users.
• Present: The mature Eclipse Platform continues as the base of the quarterly Eclipse IDE releases.

Related projects

• Eclipse Equinox supplies the OSGi runtime and secure-storage implementation.
• SWT and JFace supply the native-widget and user-interface layers.
• Eclipse JDT supplies Java development tooling.
• Eclipse PDE supports development of plug-ins and Eclipse-based products.
• Eclipse Packaging Project assembles specialized IDE downloads from the platform and other projects.

Quellen

• https://projects.eclipse.org/projects/eclipse.platform
• https://www.eclipse.org/about/
• https://www.eclipse.org/articles/Whitepaper-Platform-3.1/eclipse-platform-whitepaper.html
• https://www.eclipse.org/org/press-release/20061107eclipsebirthday5.php