macOS
Homebrew Caskverified · 100%
brew install --cask eclipse-platformlocal Homebrew cask metadata
cask
Install eclipse-platform with Homebrew Cask
SDK for the Eclipse IDE. Version 4.41,202608281142 via Homebrew Cask; verified from local package data.
install
Additional install commands
overview
Package summary
SDK for the Eclipse IDE
Project links
Commands and aliases
No executable aliases were found in the local package database.
history
Project history and usage
Eclipse SDK is the development distribution of the Eclipse Platform, the extensible component and tool-integration foundation underlying the Eclipse IDE and many Eclipse Rich Client Platform applications.
Project history
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.
Adoption history
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.
How it is used
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.
Why package nerds care
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.
Timeline
- 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.
Sources
security posture
No protected-tool coverage found yet
No matching local secret-handling manifest was found for eclipse-platform. Package metadata is still published here so future coverage has a stable package URL.
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
Configuration and credential file locations
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Configuration files
Config paths the tool may read or write during local use.
- macOS
/Applications/Eclipse.app/Contents/Eclipse/eclipse.ini/Applications/Eclipse.app/Contents/Eclipse/configuration/config.ini
Credential files
Credential-bearing paths to review before unattended agent runs.
- Unix
~/.eclipse/org.eclipse.equinox.security/secure_storage
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
| No executable data was present. | |||
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-11-04
manager version4.41,202608281142
manager updated
local dataok
upstreamnot checked
latest detectednot detected
- infoNo package-manager update timestamp was available.low confidence
- infoRelease/tag comparison is only available for GitHub repositories.https://eclipse.org/none confidence
install metadata
Package metadata
| Package key | cask:eclipse-platform |
|---|---|
| Version | 4.41,202608281142 |
| Package manager | Homebrew Cask |
| Package manager page | https://formulae.brew.sh/cask/eclipse-platform |
| Homepage | https://eclipse.org/ |
| Upstream docs | https://eclipse.org/ |
| Source archive | https://www.eclipse.org/downloads/download.php?file=/eclipse/downloads/drops4/R-4.41-202608281142/eclipse-SDK-4.41-macosx-cocoa-aarch64.dmg&mirror_id=1 |
| SHA-256 | 5d293fc45363baf7c7d38c37a007f35a8c49b99f6c6396b98ab18b4464e59d7e |
| Bottle | not recorded |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
Source database details
| Source Database | Homebrew cask API |
|---|---|
| Tap | homebrew/cask |
| Full Token | eclipse-platform |
| Names |
|
| Artifacts | |
| Deprecated | no |
| Disabled | no |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment