The initial codebase originated from IBM VisualAge.[11] 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.[12]
Eclipse was inspired by the Smalltalk-based VisualAge family of integrated development environment (IDE) products.[11] 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, North Carolina, lab developed the new product as a Java-based replacement.[14][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.[15] The original members were Borland, IBM, Merant, QNX Software Systems, Rational Software, Red Hat, SuSE, TogetherSoft, and WebGain.[16] The number of stewards increased to over 80 by the end of 2003. In January 2004, the Eclipse Foundation was created.[17]
Eclipse 3.0 (released on 21 June 2004) selected the OSGi Service Platform specifications as the runtime architecture.[18]
The Eclipse Public License (EPL) is the fundamental license under which Eclipse projects are released.[20] Some projects require dual licensing, for which the Eclipse Distribution License (EDL) is available, although use of this license must be applied for and is considered on a case-by-case basis.
Different versions of Eclipse have been given different science-related names. The versions named after Callisto, Europa, and Ganymede, which are moons of Jupiter, were followed by a version named after Galileo, the discoverer of those moons. These were followed by two sun-themed names, Helios of Greek mythology, and Indigo, one of the seven colors of a rainbow (which is produced by the sun). The version after that, Juno, has a triple meaning: a Roman mythological figure, an asteroid, and a spacecraft to Jupiter.[23]Kepler, Luna, and Mars continued the astronomy theme, and then Neon and Oxygen constituted a theme of chemical elements. Photon represented a return to sun-themed names.
As of 2018[update], the alphabetic scheme was abandoned in order to better align with the new Simultaneous Release strategy.[24] Releases are named in the format YYYY-MM to reflect the quarterly releases, starting with version 4.9 named 2018-09.[25]
Releases
Since 2006, the Foundation has coordinated an annual Simultaneous Release.[26] Each release includes the Eclipse Platform and several other Eclipse projects.
From 2008 through 2018, each Simultaneous Release had occurred on the 4th Wednesday of June. In 2018 the project switched to quarterly (13 week) YYYY-MM releases without intermediate service releases.[27]
A 1.4 level Java runtime or Java development kit (JDK) can also be used to run Eclipse. It is still possible to use a 1.3 level Java runtime or Java development kit (JDK).[31]
Oxygen.1a introduced Java 9 and Junit 5 support and Oxygen.3a introduced Java 10 support.[53]
Dropped support for the following Unix based platforms: AIX, Solaris, HP-UX and s390.[54]
From this version on, a Java 8 or newer JRE/JDK is required to run Eclipse.[47]
^There is a 3.8 release of Eclipse Juno; it is not promoted on the main downloads page, but a packaged distribution is available for download.[43] Eclipse 3.8 provides bugfixes for Indigo & adds Java 7 support, and its maintenance was dual streamed with 4.2.[44] Features and plug-ins equivalent to a packaged distribution may be added from within the IDE.
Architecture
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.[85]
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[86] 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".[87] 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 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.
Web Tools Platform
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.[90]
Modeling platform
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 into six categories:
Model Transformation includes projects using Eclipse Modeling Framework (EMF)-based models as an input to produce either a model or text as an output. Model-to-model transformation projects include 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 contain 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 include projects implementating various modeling standards used in the industry, and their toolkits. Among those projects can be found implementations of several standards:
Concrete Syntax Development contains the Graphical Modeling Framework, an Eclipse-based framework dedicated to the graphical representation of EMF-based models.[citation needed]
Abstract Syntax Development hosts the Eclipse Modeling Framework, core of most modeling projects of the Eclipse Foundation and frameworks available for the EMF like Connected Data Objects (CDO), EMF query or EMF validation.
Technology and Research includes modeling project prototypes, hosting all Eclipse Foundation modeling projects during their incubation phase.[citation needed]
Amalgam provides the packaging and integration between all available modeling tools for the Eclipse package dedicated to modeling tools.[91]
Application lifecycle management
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,[92]JIRA, Unfuddle,[93] and GitHub.[94] 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.[95] The original name of this project, "Mylar", replicated a trademark of a boPET film company, so the Eclipse Foundation changed the project name.[96]
Along with native support for OSGi, JPMS support has been added as of Java 9.[97]
Extensions
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.[98]
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.[99][100]
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.[101]
Alternative distributions
Several alternative distributions exist in the Eclipse project.
The PHP Hypertext Preprocessor (PHP) Development Tools project provides a framework for the Eclipse platform. The project encompasses all development components, including code-completion, develop PHP and facilitate extensibility. It leverages the existing Eclipse Web Tools Platform (WTP) and Dynamic Languages Toolkit (DLTK).[102]
Android Development Tools
Android Development Tools (ADT) was superseded in 2015 by the Eclipse foundation's own plugin, called Andmore: Development Tools for Android,[103] after Google discontinued development of their plug-in for the Eclipse IDE, that is designed to provide an integrated environment in which to build Android applications. ADT/Andmore extends the abilities of Eclipse to let developers set up new Android projects, create an application UI, add packages based on the Android Framework API, debug their applications using the Android SDK tools, and export signed (or unsigned) .apk files in order to distribute their applications. It is freely available to download. Google's ADT was the official IDE for Android until 2015 but was replaced by Eclipse's Andmore and the official Android Studio.[104][105] As of 2024, the project appears to be moribund, with no activity since 2017.[106]
^Darryl K. Taft (20 May 2005). "Eclipse: Behind the Name". eWeek.com. Ziff Davis Enterprise Holdings. Archived from the original on 2 January 2013. Retrieved 11 August 2008.
^Sharma, Ankur (14 February 2011). "Naming Indigo +1". Eclipse. Archived from the original on 25 February 2017. Retrieved 4 July 2016.
^"Eclipse Web Tools Platform Project". Eclipse.org. Archived from the original on 6 June 2024. Retrieved 2 May 2011. The Eclipse Web Tools Platform (WTP) project extends 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, tools to support deploying, running, and testing apps, and APIs for extending its functionality.
^(in English)"Amalgation website". 31 January 2013. Archived from the original on 19 March 2015. Retrieved 5 March 2015.
_waving.svg)
