Eclipse 4.5 Mars in the Java EE perspective
|Initial release||1.0 / 7 November 2001citation needed][|
4.6.2 (Neon.2) / 24 November 2016
4.7 (Oxygen) M4 / 8 December 2016
|Operating system||Cross-platform: Linux, Mac OS X, Solaris, Windows|
|Platform||Java SE, Standard Widget Toolkit|
|Type||Programming tool, Integrated development environment (IDE)|
|License||Eclipse Public License|
The initial codebase originated from IBM VisualAge. 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-in modules. Since Equinox, plug-ins can be plugged/stopped dynamically and are known as (OSGI) bundles
Released under the terms of the Eclipse Public License, Eclipse SDK is free and open-source software, although it is incompatible with the GNU General Public License. It was one of the first IDEs to run under GNU Classpath and it runs without problems under IcedTea.
- 1 History
- 2 Architecture
- 3 Rich Client Platform
- 4 Server platform
- 5 Web Tools Platform
- 6 Modeling platform
- 7 Extensions
- 8 Alternative distributions
- 9 See also
- 10 Further reading
- 11 Sources
- 12 References
- 13 External links
Eclipse was inspired by the Smalltalk-based VisualAge family of integrated development environment (IDE) products. Although fairly successful, a major drawback of the VisualAge products was that developed code was not in a component model; instead, all code for a project was held in a compressed lump (somewhat like a zip file but in a proprietary format called .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. 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 close to $40 million by that time. The original members were Borland, IBM, Merant, QNX Software Systems, Rational Software, Red Hat, SuSE, TogetherSoft and WebGain. The number of stewards increased to over 80 by the end of 2003. In January 2004, the Eclipse Foundation was created.
The Eclipse Public License (EPL) is the fundamental license under which Eclipse projects are released. 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.
Eclipse was originally released under the Common Public License, but was later re-licensed under the Eclipse Public License. The Free Software Foundation has said that both licenses are free software licenses, but are incompatible with the GNU General Public License (GPL).
According to Lee Nackman, Chief Technology Officer of IBM's Rational division (originating in 2003) at that time, the name "Eclipse" (dating from at least 2001) was not a wordplay on Sun Microsystems, as the product's primary competition at the time of naming was Microsoft Visual Studio (which it, Eclipse, was to eclipse).
Different versions of Eclipse have been named after 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. Kepler, Luna, and Mars continued the astronomy theme whereupon a new theme of chemical elements commenced with Neon and Oxygen.
Since 2006 the Foundation has coordinated an annual Simultaneous Release. Each release includes the Eclipse Platform as well as a number of other Eclipse projects.
As of 2008[update] each Simultaneous Release has occurred on the 4th Wednesday of June.
|Version Name||Date||Platform Version||Projects||Main Changes|
|N/A||21 June 2004||Old version, no longer supported: 3.0|
|N/A||28 June 2005||Old version, no longer supported: 3.1||Added Java 5 support (Generics, annotations, boxing/unboxing, enums, enhanced for loop, varargs, static imports)|
|Callisto||30 June 2006||Old version, no longer supported: 3.2||Callisto projects|
|Europa||29 June 2007||Old version, no longer supported: 3.3||Europa projects|
|Ganymede||25 June 2008||Old version, no longer supported: 3.4||Ganymede projects|
|Galileo||24 June 2009||Old version, no longer supported: 3.5||Galileo projects|
|Helios||23 June 2010||Old version, no longer supported: 3.6||Helios projects|
|Indigo||22 June 2011||Old version, no longer supported: 3.7||Indigo projects|
|Juno||27 June 2012||Old version, no longer supported: 3.8 and 4.2||Juno projects|
|Kepler||26 June 2013||Old version, no longer supported: 4.3||Kepler projects|
|Luna||25 June 2014||Old version, no longer supported: 4.4||Luna projects||Integrated Java 8 support (in the previous version this was possible via a "Java 8 patch" plugin)|
|Mars||24 June 2015||Old version, no longer supported: 4.5||Mars projects|
|Neon||22 June 2016||Current stable version: 4.6||Neon projects|
|Oxygen||June 2017 (planned)||Future release: 4.7||Oxygen projects|
- 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. Eclipse 3.8 provides bugfixes for Indigo & adds Java 7 support, and its maintenance was dual streamed with 4.2. Features and plugins equivalent to a packaged distribution may be added from within the IDE.
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 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. This means that every plug-in developed integrates with Eclipse in exactly the same way as other plug-ins; in this respect, all features are "created equal". Eclipse provides plug-ins for a wide variety of features, some of which are through third parties using both free and commercial models. Examples of plug-ins include for UML, for Sequence and other UML diagrams, a plug-in for DB Explorer, and many others.
The Eclipse SDK includes the Eclipse Java development tools (JDT), offering an IDE with a built-in incremental Java 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 afterwards.
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) or Swing. 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 GSoC-Project in 2014.
Rich Client Platform
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
- 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
- Novell/NetIQ Designer for Identity Manager
- Apache Directory Studio
- Remote Component Environment
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 the 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.
The Modeling project contains all the official projects of the Eclipse Foundation focusing on model-based development technologies. They are all 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 EMF based models as an input and produce either a model or text as an output. Model to model transformation projects includes 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). Acceleo is an open source code generator that can generate any textual language (Java, PHP, Python, etc.) from EMF based models defined with any metamodel (UML, SysML, etc.).
Model Development Tools projects are implementations of modeling standard used in the industry like UML or OCL and their toolkit. Among those projects can be found implementations of the following standards:
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 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.
Amalgam provides the packaging and integration between all the available modeling tools for the Eclipse package dedicated to modeling tools.
A number of alternative distributions exist in the Eclipse project.
Eclipse PDT (PHP Development Tools)
The PHP (PHP hypertext Preprocessor) Development Tools project provides a PHP Development Tools 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).
Eclipse ADT (Android Development Tools)
Android Development Tools (ADT) is a discontinued Google-provided plugin for the Eclipse IDE that is designed to provide an integrated environment in which to build Android applications. ADT extends the capabilities 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. It was the official IDE for Android but was replaced by Android Studio (based on IntelliJ IDEA Community Edition).
- Comparison of integrated development environments
- Comparison of integrated development environments for Java
- List of Eclipse-based software
- List of Eclipse projects
- How to develop an Eclipse RCP application
- How to develop an Eclipse Plug-in Part 1
- How to develop an Eclipse Plug-in Part 2
- Silva, Vladimir (11 March 2009). Practical Eclipse Rich Client Platform Projects (1st ed.). Apress. p. 352. ISBN 1-4302-1827-4.
- Burnette, Ed (12 August 2005). Eclipse IDE Pocket Guide (1st ed.). O'Reilly Media. p. 128. ISBN 978-0-596-10065-0.
- Holzner, Steve (1 May 2004). Eclipse (1st ed.). O'Reilly Media. p. 317. ISBN 0-596-00641-1.
- McAffer, Jeff; Lemieux, Jean-Michel; Aniszczyk, Chris (22 May 2010). Eclipse Rich Client Platform (2nd ed.). Addison-Wesley Professional. p. 552. ISBN 0-321-60378-8.
- Lextrait, Vincent (July 2010). "The Programming Languages Beacon, v10.3". Archived from the original on 30 May 2012. Retrieved 5 September 2010.
- "Where did Eclipse come from?". Eclipse Wiki. Retrieved 16 March 2008.
- "500 lines or less: Eclipse" says "With the switch to OSGi, Eclipse plugins became known as bundles"
- Free Software Foundation, Inc. (5 November 2012). "Various Licenses and Comments About Them".
- Rick DeNatale (15 October 2008). "Will It Go Round in Circles?". Archived from the original on 19 October 2008.
- Milinkovich, Mike. "IBM and Eclipse: A Decade of Software Innovation". Building a Smarter Planet. Retrieved 3 November 2011.
- "About the Eclipse Foundation: History of Eclipse". Eclipse. Retrieved 1 January 2014.
- "About the Eclipse Foundation". The Eclipse Foundation. Retrieved 13 August 2008.
- "OSGi – the footings of the foundation of the platform". The Eclipse Foundation. Retrieved 25 June 2008.
- "ACM Honors Computing Innovators for Advances in Research, Education, and Industry". Association for Computing Machinery. Retrieved 26 April 2012.
- "Eclipse Public License". Retrieved 24 February 2012.
- "Various Licenses and Comments about Them". Free Software Foundation. 17 May 2007. Retrieved 20 May 2007.
- Darryl K. Taft (20 May 2005). "Eclipse: Behind the Name". eWeek.com. Ziff Davis Enterprise Holdings. Retrieved 11 August 2008.
- Sharma, Ankur (14 Feb 2011). "Naming Indigo +1". eclipse.org. Retrieved 4 July 2016.
- "Eclipse Foundation". Eclipse.org. 21 June 2004. Retrieved 16 June 2013.
- "Eclipse Callisto Projects". Eclipse. Retrieved 1 February 2014.
- "Europa Simultaneous Release". Eclipsepedia. Retrieved 1 February 2014.
- "Ganymede Simultaneous Release". Eclipsepedia. Retrieved 1 February 2014.
- "Galileo Simultaneous Release". Eclipsepedia. Retrieved 1 February 2014.
- "Category:Helios". Eclipsepedia. Retrieved 1 February 2014.
- "Category:Indigo". Eclipsepedia. Retrieved 1 February 2014.
- "Eclipse Juno Release Train Has Arrived". Eclipse.org. 27 June 2012. Retrieved 16 June 2013.
- "Category:Juno". Eclipsepedia.
- "Category:Kepler". Eclipsepedia. Retrieved 1 February 2014.
- "Category:Luna". Eclipsepedia. Retrieved 1 February 2014.
- "Category:Mars". Eclipsepedia. Retrieved 4 April 2014.
- "Category:Neon". Eclipsepedia. Retrieved 20 April 2014.
- "Category:Oxygen". Eclipsepedia. Retrieved 2 February 2016.
- "OSGi Certified Products". OSGi Alliance Site. Retrieved 2016-08-02.
- "TeXlipse homepage – LaTeX for Eclipse". TeXlipse. Retrieved 1 January 2014.
- "Eclipse now runs on Wayland". 18 August 2014.
- "Babel Project – Eclipse translation". Eclipse Babel. Retrieved 1 January 2014.
- "Eclipse Web Tools Platform Project". http://eclipse.org/: Eclipse. 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.
- (English) "Amalgation website". Retrieved 5 March 2015.
- "PHP Development Tools". projects.eclipse.org. Retrieved 1 January 2014.
- Eason, Jamal. "Android Studio 1.0".
|Wikimedia Commons has media related to Eclipse IDE.|
|Wikibooks has a book on the topic of: Eclipse|