Eclipse is an integrated development environment (IDE) used in computer programming.^[5] It contains a base workspace and an extensible plug-in system for customizing the environment. It is the second-most-popular IDE for Java development, and, until 2016, was the most popular.^[6] Eclipse is written mostly in Java and its primary use is for developing Java applications,^[7] but it may also be used to develop applications in other programming languages via plug-ins, including Ada, ABAP, C, C++, C#, Clojure, COBOL, D, Erlang, Fortran, Groovy, Haskell, JavaScript, Julia,^[8] Lasso, Lua, NATURAL, Perl, PHP, Prolog, Python, R, Ruby (including Ruby on Rails framework), Rust, Scala, and Scheme. It can also be used to develop documents with LaTeX (via a TeXlipse plug-in) and packages for the software Mathematica. Development environments include the Eclipse Java development tools (JDT) for Java and Scala, Eclipse CDT for C/C++, and Eclipse PDT for PHP, among others.^[9]

Quick Facts Original author(s), Developer(s) ...

Eclipse

Welcome screen of Eclipse 4.12
Original author(s)	IBM
Developer(s)	Eclipse Foundation
Initial release	1.0 / 29 November 2001; 22 years ago (2001-11-29)[1]
Stable release	4.30.0[2]  / 6 December 2023 (4 months ago)
Repository	https://github.com/eclipse-platform/eclipse.platform
Written in	Java, C[3]
Operating system	Linux, macOS, Windows
Platform	Java SE, Standard Widget Toolkit, x86-64, AArch64
Available in	44 languages
List of languages Albanian, Arabic, Basque, Bulgarian, Catalan, Chinese (simplified, traditional), Czech, Danish, Dutch, English (Australia, Canada), Estonian, Finnish, French, German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Klingon, Korean, Kurdish, Lithuanian, Malayalam, Mongolian, Myanmar, Nepali, Norwegian, Persian, Polish, Portuguese (Portugal, Brazil), Romanian, Russian, Serbian, Slovak, Slovenian, Spanish, Swedish, Thai, Turkish, Ukrainian, Vietnamese[4]
Type	Programming tool, integrated development environment (IDE)
License	Eclipse Public License
Website	eclipseide.org

Close

The initial codebase originated from IBM VisualAge.^[10] The Eclipse software development kit (SDK), which includes the Java development tools, is meant for Java developers. Users can extend its abilities by installing plug-ins written for the Eclipse Platform, such as development toolkits for other programming languages, and can write and contribute their own plug-ins. Since Eclipse 3.0 (released in 2004), plug-ins are installed and managed as "bundles" using Equinox, an implementation of OSGi.^[11]

The Eclipse SDK is free and open-source software, released under the terms of the Eclipse Public License, although it is incompatible with the GNU General Public License.^[12] It was one of the first IDEs to run under GNU Classpath and it runs without problems under IcedTea.

Eclipse was inspired by the Smalltalk-based VisualAge family of integrated development environment (IDE) products.^[10] Although fairly successful, a major drawback of the VisualAge products was that developed code was not in a component-based software engineering model. Instead, all code for a project was held in a compressed database using SCID techniques (somewhat like a zip file but in .dat). Individual classes could not be easily accessed, certainly not outside the tool. A team primarily at the IBM Cary, NC lab developed the new product as a Java-based replacement.^{[13][failed verification]} In November 2001, a consortium was formed with a board of stewards to further the development of Eclipse as open-source software. It is estimated that IBM had already invested nearly $40 million by that time.^[14] The original members were Borland, IBM, Merant, QNX Software Systems, Rational Software, Red Hat, SuSE, TogetherSoft, and WebGain.^[15] The number of stewards increased to over 80 by the end of 2003. In January 2004, the Eclipse Foundation was created.^[16]

Eclipse 3.0 (released on 21 June 2004) selected the OSGi Service Platform specifications as the runtime architecture.^[17]

The Association for Computing Machinery recognized Eclipse with the 2011 ACM Software System Award on 26 April 2012.^[18]

Eclipse uses plug-ins to provide all the functionality within and on top of the run-time system. Its run-time system is based on Equinox, an implementation of the OSGi core framework specification.^[80]

In addition to allowing the Eclipse Platform to be extended using other programming languages, such as C and Python, the plug-in framework allows the Eclipse Platform to work with typesetting languages like LaTeX^[81] and networking applications such as telnet and database management systems. The plug-in architecture supports writing any desired extension to the environment, such as for configuration management. Java and CVS support is provided in the Eclipse SDK, with support for other version control systems provided by third-party plug-ins.

With the exception of a small run-time kernel, everything in Eclipse is a plug-in. Thus, every plug-in developed integrates with Eclipse in the same way as other plug-ins; in this respect, all features are "created equal".^[82] Eclipse provides plug-ins for a wide variety of features, some of which are from third parties using both free and commercial models. Examples of plug-ins include for Unified Modeling Language (UML), for Sequence and other UML diagrams, a plug-in for DB Explorer, and many more.

The Eclipse SDK includes the Eclipse Java development tools (JDT), offering an IDE with a built-in Java incremental compiler and a full model of the Java source files. This allows for advanced refactoring techniques and code analysis. The IDE also makes use of a workspace, in this case a set of metadata over a flat filespace allowing external file modifications as long as the corresponding workspace resource is refreshed afterward.

Eclipse implements the graphical control elements of the Java toolkit called Standard Widget Toolkit (SWT), whereas most Java applications use the Java standard Abstract Window Toolkit (AWT), Swing, or JavaFX. Eclipse's user interface also uses an intermediate graphical user interface layer called JFace, which simplifies the construction of applications based on SWT. Eclipse was made to run on Wayland during a Google Summer of Code (GSoC) Project in 2014.^[83]

As of 2017^[update], language packs being developed by the Babel Project provide translations into over 40 natural languages.^[4]

Eclipse provides the rich client platform (RCP) for developing general-purpose applications.

The following components constitute the rich client platform:

• Equinox OSGi – a standard bundling framework
• Core platform – boot Eclipse, run plug-ins^{[citation needed]}
• Standard Widget Toolkit (SWT) – a portable widget toolkit
• JFace – viewer classes to bring model view controller programming to SWT, file buffers, text handling, text editors
• Eclipse Workbench – views, editors, perspectives, wizards

Examples of rich client applications based on Eclipse are:

• IBM Notes 8 and 9
• Attachmate-Novell NetIQ Designer for Identity Manager
• Apache Directory Studio
• Remote Component Environment
• DBeaver, a SQL client software
• Portfolio Performance^[84]
• UDig, a GIS software
• AnyLogic, a multimethod simulation modeling tool

Eclipse supports development for Tomcat, GlassFish and many other servers and is often capable of installing the required server (for development) directly from the IDE. It supports remote debugging, allowing a user to watch variables and step through the code of an application that is running on the attached server.

The Eclipse Web Tools Platform (WTP) project is an extension of the Eclipse platform with tools for developing Web and Java EE applications. It includes source and graphical editors for a variety of languages, wizards and built-in applications to simplify development, and tools and APIs to support deploying, running, and testing apps.^[85]

The Modeling project contains all the official projects of the Eclipse Foundation focusing on model-based development technologies. All are compatible with the Eclipse Modeling Framework created by IBM. Those projects are separated in several categories: Model Transformation, Model Development Tools, Concrete Syntax Development, Abstract Syntax Development, Technology and Research, and Amalgam.

Model Transformation projects uses Eclipse Modeling Framework (EMF) based models as an input and produce either a model or text as an output. Model to model transformation projects includes ATLAS Transformation Language (ATL), an open source transformation language and toolkit used to transform a given model or to generate a new model from a given EMF model. Model to text transformation projects contains Acceleo, an implementation of MOFM2T, a standard model to text language from the Object Management Group (OMG). The Acceleo code generator can generate any textual language (Java, PHP, Python, etc.) from EMF based models defined with any metamodel (Unified Modeling Language (UML), Systems Modeling Language (SysML), etc.). It is open-source.

Model Development Tools projects are implementations of various modeling standards used in the industry, and their toolkits. Among those projects can be found implementations of several standards:

• Unified Modeling Language (UML)
• Systems modeling language (SysML)
• Object Constraint Language (OCL)
• Business Process Model and Notation (BPMN)
• Semantics of Business Vocabulary and Business Rules (SBVR)
• XML Schema (XSD)
• National Electronic Distributors Association (NEDA)
• Model-to-Model Transformations (MMT)

The Concrete Syntax Development project contains the Graphical Modeling Framework, an Eclipse-based framework dedicated to the graphical representation of EMF based models.^{[citation needed]}

The Abstract Syntax Development project hosts the Eclipse Modeling Framework, core of most of the modeling project of the Eclipse Foundation and the framework available for EMF like Connected Data Objects (CDO), EMF query or EMF validation.

Technology and Research projects are prototypes of Modeling project; this project is used to host all the modeling projects of the Eclipse Foundation during their incubation phase.^{[citation needed]}

Amalgam provides the packaging and integration between all the available modeling tools for the Eclipse package dedicated to modeling tools.^[86]

Application lifecycle management (ALM) and task management in Eclipse need an optional component called Mylyn (/ˈmaɪlɪn/), an open-source implementation of the task-focused interface. It provides an API for tools embedding the task-focused interface. For software developers, it helps a developer work efficiently with many different tasks (such as bugs, problem reports or new features). Tasks are integrated into Mylyn. For all tasks that have been integrated, Mylyn monitors user activity and tries to identify information relevant to the task at hand. It uses this task context to focus the Eclipse UI on the related information. Mylyn can integrate with repositories such as Bugzilla, Trac, Redmine, Mantis,^[87] JIRA, Unfuddle,^[88] and GitHub.^[89] It focuses on improving productivity by reducing searching, scrolling, and navigation. By making task context explicit, Mylyn is also meant to facilitate multitasking, planning, reusing past efforts, and sharing expertise.

The project name comes from myelin, an electrically insulating layer that surrounds neurons' axons.^[90] The original name of this project, "Mylar", replicated a trademark of a boPET film company, so the Eclipse Foundation changed the project name.^[91]

Eclipse IDE features include text editor with syntax coloring, coding assistance, code completion, code refactoring, code analysis with "Quick fix" suggestions along with code debugging.^[92]

Along with native support for OSGi, JPMS support has been added as of Java 9.^[92]

Eclipse supports a rich selection of extensions, adding support for Python via PyDev, Android development via Google's ADT (superseded by Android Studio since 2015), JavaFX via e(fx)clipse, JavaScript, jQuery, and many others at the Eclipse Marketplace. Valable is a Vala plug-in for Eclipse.^[93]

In addition to the built in Java compiler warnings, additional plug-ins are available for linting to improve code quality and consistency such as SpotBugs and Sonar.^[94][95]

Support for build tools such as Ant, Maven, Make, and CMake includes the capability to replace Eclipse native project file format with Maven pom.xml directly.^[96]

Several alternative distributions exist in the Eclipse project.

• Comparison of integrated development environments
• Comparison of integrated development environments for Java
• List of Eclipse-based software
• List of Eclipse projects