Screenshot of Eclipse 3.7.2 |
|
Developer(s) | Free and open source software community |
---|---|
Stable release | 3.7.2 Indigo / 24 February 2012 |
Development status | Active |
Written in | Java |
Operating system | Cross-platform: Linux, Mac OS X, Solaris, Windows |
Platform | Java SE, Standard Widget Toolkit |
Available in | Multilingual |
Type | Software development |
License | Eclipse Public License |
Website | www.eclipse.org |
Eclipse is a multi-language software development environment comprising an integrated development environment (IDE) and an extensible plug-in system. It is written mostly in Java. It can be used to develop applications in Java and, by means of various plug-ins, other programming languages including Ada, C, C++, COBOL, Perl, PHP, Python, R, Ruby (including Ruby on Rails framework), Scala, Clojure, Groovy and Scheme. It can also be used to develop packages for the software Mathematica. Development environments include the Eclipse Java development tools (JDT) for Java, Eclipse CDT for C/C++, and Eclipse PDT for PHP, among others.
The initial codebase originated from VisualAge.[1] The Eclipse 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.
Released under the terms of the Eclipse Public License, Eclipse SDK is free and open source software. It was one of the first IDEs to run under GNU Classpath and it runs without issues under IcedTea.
Contents |
History
Eclipse began as an IBM Canada project. Object Technology International (OTI), which had previously marketed the Smalltalk-based VisualAge family of IDE products,[1] developed the new product as a Java-based replacement.[2] In November 2001, a consortium was formed with a board of stewards to further the development of Eclipse as open-source software. The original members were Borland, IBM, Merant, QNX Software Systems, Rational Software, Red Hat, SuSE, TogetherSoft and WebGain. [3]The number of stewards increased to over 80 by the end of 2003. In January 2004, the Eclipse Foundation was created.[4]
Eclipse 3.0 (released on 21 June 2004) selected the OSGi Service Platform specifications as the runtime architecture.[5]
The Association for Computing Machinery recognized Eclipse with the 2011 ACM Software Systems Award on 26 April 2012.[6]
Licensing
The Eclipse Public License (EPL) is the fundamental license under which Eclipse projects are released.[7] 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.
The Eclipse SDK was originally released under the Common Public License, but was later relicensed 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).[8] Mike Milinkovich, of the Eclipse Foundation commented that moving to the GPL would be considered when version 3 of the GPL was released.[9]
Name
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.[10]
Releases
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.
So far, each Simultaneous Release has occurred on the fourth Wednesday of June.
Codename | Date | Platform version | Projects |
---|---|---|---|
? | 21 June 2004 | 3.0 [1] | |
? | 28 June 2005 | 3.1 | |
Callisto | 30 June 2006 | 3.2 | Callisto projects |
Europa | 29 June 2007 | 3.3 | Europa projects |
Ganymede | 25 June 2008 | 3.4 | Ganymede projects |
Galileo | 24 June 2009 | 3.5 | Galileo projects |
Helios | 23 June 2010 | 3.6 | Helios projects |
Indigo | 22 June 2011 | 3.7 | Indigo projects |
Juno | 27 June 2012 (scheduled) | 3.8 and 4.2 | Juno projects |
Kepler | June 2013 (planned) | 4.xx | Kepler projects |
Architecture
The Eclipse Platform uses plug-ins to provide all functionality within and on top of the runtime system, in contrast to some other applications, in which functionality is hard coded. The Eclipse Platform's runtime system is based on Equinox, an implementation of the OSGi core framework specification.
This plug-in mechanism is a lightweight software componentry framework. 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,[11] 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".[citation needed] 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 a UML plug-in 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 widgets through a widget toolkit for Java called SWT, unlike most Java applications, which 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.
Language packs provide translations into over a dozen natural languages.[12][citation needed]
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[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
Server platform
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.[13]
Modeling Platform
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
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 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
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 implementation of the following standard:
Concrete Syntax Development
The Concrete Syntax Development project contains the Graphical Modeling Framework, an Eclipse based framework dedicated to the graphical representation of EMF based models.
Abstract Syntax Development
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
Technology and Research projects are prototypes of Modeling project, this project is used to host all the modeling project of the Eclipse Foundation during their incubation phase.
Amalgam
Amalgam provides the packaging and integration between all the available modeling tools for the Eclipse package dedicated to modeling tools.
See also
- Comparison of integrated development environments
- Comparison of integrated development environments for Java
- List of Eclipse-based software
- List of Eclipse projects
- NetBeans
References
- ^ a b "Where did Eclipse come from?". Eclipse Wiki. http://wiki.eclipse.org/FAQ_Where_did_Eclipse_come_from%3F. Retrieved 16 March 2008.
- ^ Rick DeNatale (15 October 2008). "Will It Go Round in Circles?". http://talklikeaduck.denhaven2.com/articles/2008/10/15/will-it-go-round-in-circles.
- ^ About the Eclipse Foundation:History of Eclipse
- ^ "About the Eclipse Foundation". The Eclipse Foundation. http://www.eclipse.org/org. Retrieved 13 August 2008.
- ^ "OSGi — the footings of the foundation of the platform". The Eclipse Foundation. http://www.eclipse.org/osgi/. Retrieved 25 June 2008.
- ^ "ACM Honors Computing Innovators for Advances in Research, Education, and Industry". Association for Computing Machinery. http://www.acm.org/press-room/news-releases/2012/technical-awards-2011. Retrieved 26 April 2012.
- ^ "Eclipse Public License". http://www.eclipse.org/org/documents/epl-v10.php. Retrieved 2012-02-24.
- ^ "Various Licenses and Comments about Them". Free Software Foundation. 17 May 2007. http://www.gnu.org/licenses/license-list.html. Retrieved 20 May 2007.
- ^ Peter Galli (2 November 2005). "Moglen: GPL 3.0 Rewrite Drive Is No Democracy". eWeek. http://www.eweek.com/article2/0,1895,1881088,00.asp. Retrieved 20 May 2007.
- ^ Darryl K. Taft (20 May 2005). "Eclipse: Behind the Name". eWeek.com. Ziff Davis Enterprise Holdings. http://www.eweek.com/c/a/Application-Development/Eclipse-Behind-the-Name. Retrieved 11 August 2008.
- ^ TeXlipse homepage – LaTeX for Eclipse
- ^ Eclipse Babel Project
- ^ "Eclipse Web Tools Platform Project". http://eclipse.org/: Eclipse. http://eclipse.org/projects/project_summary.php?projectid=webtools. 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."
Further reading
Bibliography
- Silva, Vladimir (11 March 2009). Practical Eclipse Rich Client Platform Projects (1st ed.). Apress. p. 352. ISBN 1-4302-1827-4. http://www.apress.com/9781430218272.
- Burnette, Ed (12 August 2005). Eclipse IDE Pocket Guide (1st ed.). O'Reilly Media. p. 128. ISBN 978-0-596-10065-0. http://oreilly.com/catalog/9780596100650.
- Holzner, Steve (1 May 2004). Eclipse (1st ed.). O'Reilly Media. p. 317. ISBN 0-596-00641-1. http://oreilly.com/catalog/9780596006419.
- Gallardo, David; Burnette, Ed; McGovern, Robert (15 May 2003). Eclipse in Action: A Guide for the Java Developer (7th ed.). Manning Publications. p. 380. ISBN 978-1-930110-96-0. http://www.manning.com/gallardo/.
- 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. http://eclipsercp.org/2010/04/eclipse-rcp-2nd-edition-going-to-press/.
External links
|
|