Before Eclipse is ready to use

Source: Internet
Author: User

    • Release process for Eclipse

M1 08/19/2009
M2 09/30/2009
M3 11/11/2009
M4 12/16/2009
M5 02/03/2010
M6 03/17/2010 API Freeze
M7 05/05/2010 Feature Freeze
RC1 05/19/2010
RC2 05/26/2010
RC3 06/02/2010
RC4 06/09/2010
Final 06/16/2010
Helios 06/23/2010

You can see the points of M, RC, final:
M refers to the milestone (milestone) version, when possible features, APIs are refined and added, this time out of the version will be added in the name M, such as 3.7.0 M3 or 3.7M3A2, etc.
RC refers to release (release) version, when the function and API are stable, into the final test and bug repair phase, this time the version name will have RC or R tags, such as 3.6.0r3
Final final is the final stable version, that is, the release of the official version, this time the name will no longer have M and R.

    • Different version types

The Eclipse IDE for Java Developers is developed for Java
Eclipse IDE for Java EE developers is developed for EE
Eclipse for rcp/plug-in developers is developed for RCP and plug-ins
The Eclipse IDE for C/s + + developers is developed for C + +

The Eclipse classic 3.3.2 is its classical version

    • Download Install eclipse

Log in to Eclipse's official website http://www.eclipse.org, then click Downloads to access the download screen, which has information on each version, with Windows 32Bit Windows 64Bit behind each version This is to let you choose your computer is 32-bit or 64-bit, choose one, enter the download interface, directly decompression can be used.

As a Java developer, the most familiar tool is non-eclipse, here's the release and development process for eclipse:

Eclipse was originally developed by IBM as an alternative business software for the next Generation IDE development environment of Visual age for Java, which was contributed to the open source community in November 2001 and is now made up of the non-profit software vendor Alliance Eclipse Foundation (eclipse Foundation) management. In 2003, Eclipse 3.0 chose the OSGi Service platform specification as the runtime schema.

November 7, 2001, Eclipse 1.0 released

Six months later, June 27, 2002, Eclipse entered the 2.0 era. Eclipse of the 2.0 era experienced 2.0 and 2.1 two large versions. Of these, 2.0 were followed by the introduction of 2.0.1 and 2.0.2, followed by the release of the 2.1 version on March 27, 2003, with the introduction of 2.1.1,2.1.2 and 2.1.33 subsequent revisions.

June 25, 2004 is a memorable day for Eclipse, with the OSGi runtime architecture being introduced into Eclipse 3.0. The Eclipse Foundation was established this year, which also marks the beginning of Eclipse's coming into a new era. After 3.0 there are two small revisions of 3.0.1 and 3.0.2. For detailed release time information, please refer to Eclipse official website http://archive.eclipse.org/eclipse/downloads/index.php

June 27, 2005 Eclipse 3.1 was released, specifically to mention 3.1, because from this version until the release of the 3.5 version, the formation of a Jupiter satellite name-related series. In 1610, the famous scientist Galileo Galilei, through the observation of the Europa 1-Ganymede 4, presented evidence against Geocentric, and Ganymede 1-Ganymede 4 is also known as Galileo's four moons (and many other satellites later discovered by Jupiter). The four moons were also given the names of four mythical characters:

1. Europa 1:io, Theo

2. Ganymede 2:europa, Europa

3. Ganymede 3:ganymede, Genimide. (It is worth mentioning that earlier than Galileo 2000 years ago, there is a record that the Warring States period of China's Gander in 346 BC discovered the Europa 3)

4. Europa 4:callisto, Calisto

One of the most important reasons to take the names of these four people is that these four characters are famous for their beauty.

But Eclipse's naming from 3.1 to 3.4 (codename) is not in the order of Europa 1-4, but on the order of the four satellites from Jupiter from near to far, so Eclipse 3.1 is named after the 1th nearest 1--io in Jupiter's known satellite, eclipse 3.2 Using the Europa 4--callisto

The following is a known version code:

Eclipse 1.0 November 7, 2001 (win32/linux32 Motif)

Eclipse 2.0 June 27, 2002 (Linux32 Motif + GTK, and Solaris/qnx/aix)

Eclipse 2.1 March 27, 2003 (OSX first version)

Eclipse 3.0 June 25, 2004 (first OSGi version)

Eclipse 3.1 June 27, 2005 version Code IO "Europa 1, Yi ao"

Eclipse 3.2 June 26, 2006 version code Callisto "Europa Four, Calisto"

Eclipse 3.3 June 27, 2007 version Code Eruopa "Europa-II, Euro-Europa"

Eclipse 3.4 June 25, 2008 version Code Ganymede "Ganymede, Genimide"

Eclipse 3.5 June 24, 2009 version Code Galileo "Galileo"

Eclipse 3.6 June 23, 2010 Version Code Helios "Sun god"

Eclipse 3.7 June 22, 2011 Version Code Indigo "Indigo"

Eclipse 3.8/4.2 June 27, 2012 version code Juno "Wedding Star"

Eclipse 4.3 June 26, 2013 version code Kepler "Kepler"

Eclipse 4.4 June 25, 2014 version codenamed Luna "Moon God"

Since the release of Callisto in 2006, Eclipse has insisted on a tradition of publishing in the last week or the penultimate week of every June, but the Eclipse platform continues to release a version of the tradition every year from 2001 onwards.

Always feel that you know too little, even if you always work the IDE.

: http://www.eclipse.org/downloads/

The Eclipse IDE for Java Developers is developed for Java

Eclipse IDE for Java EE developers is developed for EE

Eclipse for rcp/plug-in developers is developed for RCP and plug-ins

Eclipse IDE for C + + developers is the classic version of Eclipse Classic 3.3.2 developed for C/s + +
The differences between the editions:
Eclipse IDE for Java Developers is an eclipse platform plus JDT plugin for Java development
Eclipse IDE for Java EE Developers should be Eclipse's platform plus WTP plugin for Java Enterprise-class development
Eclipse IDE for C + + developers is Eclipse's platform plus CDT plugin for C and C + + development
Eclipse for rcp/plug-in developers is the SDK for Eclipse, used primarily for plug-in development
Eclipse Classic is the original eclipse, or is mainly used to develop Java

So what is the difference between them, the biggest difference is the title and the size of the package is different. After downloading the extract, you will find that the different versions of Eclipse are different from the files in the Plugins/features directory.

A standard eclipse, add some plugins that JEE development needs, such as WTP,WST, and so on, it turns into "Eclipse IDE for Java EE". The rest is the same. As a skilled eclipse user, whichever you choose, the plugin you need can be easily accessible from the Eclipse website.
Here is a detailed description of the SDK version and runtime binary differences.

· The SDK, which appears to be the abbreviation for Software Development Toolkit, is a developer kit that contains source code.

· Runtime binary is just a run-time environment.

Many times, we need to look at Eclipse Plartform API or class source codes, for the SDK version of Eclipse, comes with the source plugin plug-in, Eclipse will directly link to us, This is very convenient for developers. If unfortunately you use binary runtime,eclipse will prompt you source can not find, need to manually link.

It is also OK to select a package with source. However, it is recommended to go to eclipse to download the corresponding Source-plugin, put in the plugins directory or dropins directory, restart the next to view the source code.

For the previously mentioned download version, Eclipse Classic is a version of the SDK with source, others do not seem to have source, (presumably because of the addition of too many other plugin, save space) need to download. For the 3.7 version, all packages can be found here http://download.eclipse.org/eclipse/downloads/drops/R-3.7-201106131736/index.php, other versions and so on.

Personal general use Eclipse Classic, need other plug-ins, to configure their own

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.