LLMpediaThe first transparent, open encyclopedia generated by LLMs

Eclipse Marketplace

Generated by GPT-5-mini
Note: This article was automatically generated by a large language model (LLM) from purely parametric knowledge (no retrieval). It may contain inaccuracies or hallucinations. This encyclopedia is part of a research project currently under review.
Article Genealogy
Parent: Adobe Dreamweaver Hop 4
Expansion Funnel Raw 74 → Dedup 0 → NER 0 → Enqueued 0
1. Extracted74
2. After dedup0 (None)
3. After NER0 ()
4. Enqueued0 ()
Eclipse Marketplace
NameEclipse Marketplace
DeveloperEclipse Foundation
Released2008
Latest release(varies)
Operating systemCross-platform
Programming languageJava
LicenseEPL

Eclipse Marketplace is a software portal and client for discovering, installing, and managing software extensions for the Eclipse IDE family. It provides a catalog of add-ons from vendors and independent contributors, and integrates with the Eclipse Foundation's projects and the broader Open Source tooling landscape. The service connects users to artifacts produced by organizations such as IBM, Red Hat, Google, Microsoft (via tooling vendors), and numerous independent projects.

Overview

Eclipse Marketplace serves as an ecosystem hub for add-ons compatible with Eclipse IDE, Eclipse Che, and related runtimes. It lists plugins, integrations, and distributions produced by corporate contributors like IBM Rational, Red Hat JBoss, and Oracle as well as community efforts tied to projects such as JUnit, Maven, Gradle, GitLab, GitHub, and Docker. The client component historically shipped as part of various Eclipse release trains, aligning with releases like Eclipse Europa, Eclipse Helios, and Eclipse Galileo to surface solutions for development stacks including Java Development Kit, C/C++, Python, and JavaScript tooling.

History and development

Marketplace emerged in the wake of initiatives to streamline plugin distribution for the Eclipse Project and coordinate third-party contributions from vendors like BEA Systems and Borland. Early development intersected with hosting services such as SourceForge and later with modern platforms like GitHub and GitLab as contributors migrated code. The Marketplace concept paralleled package distribution efforts exemplified by CPAN and RubyGems and drew lessons from installer ecosystems like Microsoft Visual Studio Gallery and NetBeans Plugin Portal. Over time, governance and contribution models evolved with influences from entities including the Eclipse Foundation, Apache Software Foundation, and corporate stakeholders such as SAP.

Features and architecture

The Marketplace architecture combines a web catalog, metadata descriptors, and an in-client installer that interacts with p2, the provisioning platform used by Eclipse Rich Client Platform and Equinox. Metadata includes manifests referencing features, bundles, and repository endpoints often hosted on platforms like Maven Central or vendor servers run by IBM and Red Hat. The client supports dependency resolution, update checks, and integration with Eclipse update manager workflows; it interoperates with build tools and CI systems such as Jenkins, Travis CI, and GitHub Actions for continuous delivery of plugins. Security and signing mechanisms mirror practices used by OpenJDK adoptors and distributions maintained by organizations like AdoptOpenJDK and Eclipse Adoptium.

Usage and integration

Developers access the Marketplace through the Eclipse IDE's Help menu or via the web catalog to discover tooling from vendors including SpringSource, IntelliJ IDEA-ecosystem providers (third-party integrations), and cloud tooling from Amazon Web Services, Google Cloud Platform, and Microsoft Azure partners. Integration points enable installing language servers (LS) aligned with Language Server Protocol adopters and connectors to version control systems such as Git, Subversion, and platforms like GitHub and Bitbucket (Atlassian). Enterprises often integrate Marketplace workflows into provisioning scripts alongside configuration management tools like Ansible and Puppet and CI pipelines driven by Jenkins or Azure DevOps.

Community and ecosystem

The Marketplace reflects contributions from foundations, corporations, and independent maintainers tied to projects including Spring Framework, Hibernate, JUnit, Mockito, Lombok, and tools for Kubernetes and OpenShift. Vendor ecosystems such as Red Hat and IBM publish commercial and open plugins, while individual developers export offerings hosted on GitHub or GitLab. Community events like EclipseCon, FOSDEM, and OSCON provide venues for showcasing Marketplace projects, and coordination often involves working groups formed under the Eclipse Foundation or collaborating projects such as Jakarta EE and CDT.

Security and governance

Security posture and governance derive from policies set by the Eclipse Foundation and best practices observed by upstream projects like Apache Software Foundation and distributions managed by organizations such as Red Hat and IBM. Code provenance, cryptographic signing, and vulnerability disclosure processes are influenced by standards in ecosystems including OpenSSF and incident response patterns seen in projects like Linux Kernel and OpenSSL. Marketplace listings typically include metadata about contributors and licensing (e.g., Eclipse Public License), and maintainers coordinate updates to address CVEs disclosed through databases maintained by entities like MITRE and advisories from vendors including Oracle and Red Hat.

Category:Software distribution platforms