- FAQ 1: What is Eclipse?
- FAQ 2: What is the Eclipse Platform?
- FAQ 3: Where did Eclipse come from?
- FAQ 4: What is the Eclipse Foundation?
- FAQ 5: How can my users tell where Eclipse ends and a product starts?
- FAQ 6: What are Eclipse projects and technologies?
- FAQ 7: How do I propose my own project?
- FAQ 8: Who is building commercial products based on Eclipse?
- FAQ 9: What open source projects are based on Eclipse?
- FAQ 10: What academic research projects are based on Eclipse?
- FAQ 11: Who uses Eclipse in the classroom?
- FAQ 12: What is an Eclipse Innovation Grant?
- FAQ 13: What Eclipse newsgroups are available?
- FAQ 14: How do I get access to Eclipse newsgroups?
- FAQ 15: What Eclipse mailing lists are available?
- FAQ 16: What articles on Eclipse have been written?
- FAQ 17: What books have been written on Eclipse?
- FAQ 18: How do I report a bug in Eclipse?
- FAQ 19: How can I search the existing list of bugs in Eclipse?
- FAQ 20: What do I do if my feature request is ignored?
- FAQ 21: Can I get my documentation in PDF form, please?
- FAQ 22: Where do I find documentation for a given extension point?
- FAQ 23: How is Eclipse licensed?
FAQ 3: Where did Eclipse come from?
Eclipse started out as proprietary technology, led by IBM’s subsidiary, Object Technology International (OTI). IBM wanted to reduce the large number of incompatible development environments being offered to its customers and to increase the reuse of the common components in those environments. By using the same common framework, development teams could leverage one another’s components, integrate to a high degree, and allow developers to roam among projects.
Eclipse did not emerge from thin air but evolved from a long product line of development environments, of which the earlier ones are IBM VisualAge for Smalltalk and IBM VisualAge for Java. Both of these products were written in Smalltalk. The IBM VisualAge Micro Edition product was the first serious—and actually quite successful—experiment with writing the entire IDE in Java. Many concepts found in Eclipse have been tried out in that product already. However, for third parties, it proved difficult to extend the product with new components, mainly for two reasons: (1) it was not designed with a component model in mind, and (2) it essentially was a monolithic, closed-source product.
A small team of experts set out to take the experiences of the previous years of designing and implementing development environments. The result was Eclipse, a platform designed from the ground up as an integration platform for development tools. It enabled partners to easily extend products built on it, using the plug-in mechanisms provided by the platform. The subsequent path to open source and enabling of a much wider audience and ecosystem was a natural progression.
The Eclipse open source project was announced in November 2001 by a group of companies that formed the initial Eclipse Consortium. From there, the small initial project burgeoned into a collection of related projects that formed the basis of dozens of commercial applications.