pkg.soopen package index

cask

eclipse-java mit Homebrew Cask installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für eclipse-java in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrew Caskverifiziert · 100%
brew install --cask eclipse-java

local Homebrew cask metadata

Überblick

Paketzusammenfassung

Eclipse IDE for Java developers

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Verlauf

Projektgeschichte und Nutzung

Eclipse IDE for Java Developers is the Eclipse Packaging Project's general-purpose Java distribution, combining Eclipse JDT with Git, Maven, Gradle, XML, terminal, code-coverage, and setup tooling.

Projektgeschichte

IBM created the Eclipse Project in November 2001 and released it as open source with support from a vendor consortium. The Eclipse Foundation was created in 2004 as an independent, vendor-neutral steward.

The Eclipse Packaging Project later standardized ready-to-use downloadable editions. The Java Developers package centers on the Eclipse Java Development Tools and bundles commonly expected source-control and build integrations.

Adoptionsgeschichte

Eclipse became one of the best-known Java development environments after IBM released the project as open source. Its extensible plug-in model supported a large tooling ecosystem, while the packaged Java edition provided a predictable starting point for application developers.

The current Java package combines JDT with Git, Maven, Gradle, XML, code-coverage, terminal, and setup tooling, reducing the need for users to assemble these features individually.

Wie es verwendet wird

Java developers use the package to create, edit, compile, test, run, debug, and version-control Java projects, including projects built with Maven or Gradle.

Eclipse stores most workspace-specific preferences and metadata inside the selected workspace. JVM and launcher options are configured in `eclipse.ini`; in a macOS application bundle the file resides under `Contents/Eclipse`.

Warum Paket-Nerds sich dafür interessieren

This cask installs a specific Eclipse Packaging Project composition, not merely the base Eclipse Platform. That composition is built from independently maintained Eclipse features and a simultaneous-release repository.

For package enthusiasts, Eclipse is a classic example of layered package management: Homebrew installs the macOS product, EPP defines the product, and Eclipse p2 manages plug-ins and updates within it.

Zeitleiste

  • 2001: IBM created and open-sourced the Eclipse Project.
  • 2004: The Eclipse Foundation became the project's independent steward.
  • 2024: Current EPP generations moved to a bundled Java 21 runtime.
  • 2026: EPP continued publishing the Java Developers package in quarterly simultaneous releases.

Related projects

  • Eclipse Platform: The extensible desktop workbench.
  • Eclipse JDT: The Java compiler, editor, debugger, and associated development tooling.
  • Eclipse Packaging Project: Defines and builds this downloadable product.
  • EGit, m2e, and Buildship: Bundled Git, Maven, and Gradle integrations.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für eclipse-java wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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
<Eclipse.app>/Contents/Eclipse/eclipse.ini

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
Es waren keine Executable-Daten vorhanden.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-11-04
Manager-Version4.41,2026-09
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://eclipse.org/

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz
  • InfoRelease/tag comparison is only available for GitHub repositories.https://eclipse.org/none Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselcask:eclipse-java
Version4.41,2026-09
PaketmanagerHomebrew Cask
Paketmanager-Seitehttps://formulae.brew.sh/cask/eclipse-java
Homepagehttps://eclipse.org/
Upstream-Dokumentationhttps://eclipse.org/
Quellarchivhttps://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2026-09/R/eclipse-java-2026-09-R-macosx-cocoa-aarch64.dmg&r=1
SHA-256417e86d866f053d0590a55213e440bf50233a77ed2a9a40680eff37a0b883e50
Bottlenicht erfasst
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokeneclipse-java
Names
  • Eclipse IDE for Java Developers
Artifacts
Deprecatedno
Disabledno

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment