Eclipse is a free integrated development environment for modular cross-platform applications. Developed and supported by the Eclipse Foundation.
The most well-known applications based on the Eclipse Platform are the various “Eclipse IDEs” for software development in multiple languages (for example, the most popular “ Java IDE", supported natively, does not rely on any proprietary extensions, uses the standard open API to access the Eclipse Platform).
Eclipse was originally developed by IBM as a successor to the IBM VisualAge development environment, as a corporate IDE standard for development on different languages for IBM platforms. According to IBM, design and development cost $40 million. The source code was fully open sourced and made available after Eclipse was made available to further development community independent from IBM.
Eclipse 3.0 (2003) adopted the OSGi service platform specifications as the runtime architecture. Since version 3.0, Eclipse has ceased to be a monolithic IDE that supports extensions, and itself has become a collection of extensions. It is based on the OSGi and SWT/JFace framework, on the basis of which the next layer is developed - RCP (Rich Client Platform, a platform for developing full-fledged client applications). RCP serves as the basis not only for Eclipse, but also for other RCP applications such as Azureus and File Arranger. The next layer is Eclipse itself, which is a set of RCP extensions - editors, panels, perspectives, the CVS module and the Java Development Tools (JDT) module.
Since 2006, the Eclipse Foundation has coordinated an annual Simultaneous Release, which occurs in June. Each release includes the Eclipse platform as well as a number of other Eclipse projects.
Eclipse Benefits
Eclipse primarily serves as a platform for developing extensions, which is why it has gained popularity: any developer can extend Eclipse with his own modules. There are already Java Development Tools (JDT), C/C++ Development Tools (CDT), developed by QNX engineers together with IBM, and tools for Ada languages (GNATbench, Hibachi), COBOL, FORTRAN, PHP, etc. from various developers. Many extensions complement the Eclipse environment with managers for working with databases, application servers, etc.
Eclipse JDT (Java Development Tools) is the most famous module aimed at group development: the environment is integrated with version control systems CVS, GIT in the main distribution, and there are plugins for other systems (for example, Subversion, MS SourceSafe). Also offers support for communication between the IDE and the task (error) management system. The main package includes support for the Bugzilla bug tracker, and there are also many extensions to support other trackers (Trac, Jira, etc.). Due to free and High Quality,Eclipse is the corporate standard for application development in many organizations.
Eclipse is written in Java, therefore it is a platform-independent product, with the exception of the SWT library, which is developed for all common platforms (see below). The SWT library is used instead of the standard Java Swing library. It relies entirely on the underlying platform (operating system), which ensures fast and natural appearance user interface, but sometimes causes compatibility and application stability issues across platforms.
The basis of Eclipse is the rich client platform (RCP). It consists of the following components:
OSGi (standard bundles delivery environment);
SWT (portable widget toolkit);
JFace (file buffers, working with text, text editors);
Eclipse work environment (panels, editors, projections, wizards).
The GUI in Eclipse is written using the SWT toolkit. The latter, unlike Swing (which independently emulates graphical controls), uses the graphical components of this operating system. The Eclipse user interface also depends on a GUI middleware called JFace, which makes it easy to build an SWT-based user interface.
Eclipse's flexibility is ensured by plug-ins, which makes it possible to develop not only in Java, but also in other languages, such as C/C++, Perl, Groovy, Ruby, Python, PHP, Erlang, Component Pascal, Zonnon and others.
Java Platform
Java Software Platform - Series software products and specifications from Sun Microsystems, a formerly independent company and now a subsidiary of Oracle Corporation, which together provide a system for application development software and embedding it into any cross-platform software. Java is used in a wide variety of computer platforms from embedded devices to mobile phones in the lower price segment, to corporate servers and supercomputers in the highest price segment. Although Java applets are rarely used in desktop computers, however, they are sometimes used to improve functionality and security when browsing the World Wide Web.
Program code written in Java is converted by the Java Virtual Machine into Java bytecode. However, there are bytecode compilers for other programming languages, such as Ada, JavaScript, Python, and Ruby. There are also several new programming languages designed to work with virtual machine Java. These are languages such as Scala, Clojure and Groovy. Java's syntax is largely derived from C and C++, but its object-oriented capabilities are based on the model used in Smalltalk and Objective-C. Java lacks certain low-level constructs such as pointers, and Java also has very simple model memory, where each object is located on the heap and all object type variables are references. Memory management is done through integrated automatic garbage collection performed by the JVM.
What does IBM's contribution to the open source community mean to you?
Marc Erickson and Angus McIntyre
Published 11/01/2001
The Eclipse platform is designed for building integrated development environments (IDEs). It can be used to create a variety of end-to-end computing solutions for a variety of runtime environments. When choosing an architecture, tool creators need:
- Level playing field and full disclosure with no hidden APIs or interfaces from tool to tool. Eclipse offers an open source platform for this purpose. To ensure code quality, portability, and performance, published APIs are tested by a consortium of related industries.
- Freedom to expand the platform to achieve new possibilities. Eclipse provides the ability to create derivative works, including platform redistribution. Using Eclipse allows tool developers to focus on their core tasks and new models for development technology.
- Receive timely responses to requests for product changes and improvements, delivered in a controlled and organized manner. Developers can make various changes through www.eclipse.org. This is achieved through collaboration and all possible assistance from developers in the development of the platform.
Questions and answers
- Facilitate seamless integration of internal tools as well as between various types content and tool providers.
- Support for creating a variety of tools.
- Supports an unlimited number of tool vendors, including independent software vendors (ISVs).
- Supports tools for working with any format (including HTML, Java, C, JSP, EJB, XML and GIF).
- Supports application development environments with and without graphical user interface (GUI).
- Runs on a wide range of operating systems, including Windows and Linux.
- Leveraging the popularity of the Java language to write tools.
Will IBM release the Eclipse platform source code to the open community? When will this happen?
Yes, the source code is available now under the Common Public License. Very soon, IBM will transition Eclipse to an interim board of directors that will oversee the Eclipse platform.
Who is on the interim board of directors?
The interim council will be announced later.
I want to join the community. How to do it?
Visit www.eclipse.org.
How to become a council member?
Collaborate, contribute, assist: offer code, ideas, products, bug fixes, exchange knowledge and experience.
How is the Eclipse platform supported?
Support is provided through the forum and e-mail on a voluntary basis, using resources recognized by the community. detailed information located at www.eclipse.org
Is there 24/7 support?
On what basis is the interim board of directors elected?
With limited staff, the Eclipse team can only interact with the select few companies chosen to build the platform. Members of the interim board of directors are selected from companies that have contributed to the development of the platform, on a trial basis for now. There are three criteria for selection: board members must be using Eclipse in their company; they should also use Eclipse to create commercial offers; they should openly support Eclipse.org.
Why did you delay releasing the Eclipse source code for so long?
Once the company's plans for delivering the source code were carefully examined, the development team wanted to ensure that the first platform was thoroughly developed and thoroughly tested. We have tested several alternative construction concepts, some of which are already on the market. We subsequently shared these ideas with other tool providers and improved them. The Eclipse platform is now ready for its first release.
When IBM releases a technology for free distribution, does that mean that IBM is no longer committed to that technology?
IBM is committed to adopting the Eclipse platform and using it as the basis for IBM's entire family of end-to-end software development tools, which is the WebSphere Studio family. These products benefit from integrated quality assurance, legendary IBM product support, and our commitment to the IBM brand. They use similar interfaces and are built on technology common to the Eclipse platform.
Where can I find documentation and information about Eclipse?
At www.eclipse.org.
How different is Eclipse from .NET?
.NET technology was created exclusively for use on Microsoft platforms through a proprietary interface imposed by Microsoft. Developers must respond to changes in .NET. In a world characterized as more than "wintel" technology, the .NET platform is a significant inconvenience. End-to-end computing projects that need to integrate servers, workstations, embedded devices, and handheld PCs run on a variety of other highly mature and advanced runtime environments. This leads to the use of many powerful processor architectures and operating platforms such as OS/390, Linux and QNX.
The Eclipse platform is available under an open public license with all clearly documented APIs and extension points, so it allows tool developers to support any number of desktop environments, including Microsoft products.
How does Eclipse compare to Sun Microsystems' Open Source initiative?
The Eclipse project's vision is to create an "Apache for developer tools." This means creating an open source infrastructure that provides many of the basic services that software developers need. This should be a "toolkit for developing toolkits". More than just a collection of APIs, the Eclipse framework will consist of actual code written to do real work.
As Erich Gamma states: "Everything in Eclipse is a plugin. The Java IDE has no special status, it is just another set of plugins that demonstrate the easily integrated extensibility of the platform. Making the Eclipse platform open source allows tool creators to do the same and not only to create new plugins, but also to help improve existing ones. As a result, large enterprises and enterprise representatives have equal conditions for integrating tools."
What are the differences between WebSphere Studio Workbench and the Eclipse platform?
WebSphere Studio Workbench uses Eclipse as the foundation to provide product integrations that support the WebSphere software platform. WebSphere Studio Workbench is an example of using Eclipse technology from the Eclipse platform.
Eclipse is an open source tool integration platform available for use in any work environment.
They differ in four main ways:
Support
Support for the Eclipse platform is provided through the Eclipse.org consortium, while support for WebSphere is provided by the standard framework IBM support(PartnerWorld).
Licensing
The Eclipse platform is available under the Common Public License, while WebSphere Studio Workbench is available under the IBM PartnerWorld License.
By-products/Source code modifications
The Eclipse platform allows tool developers to explore new frontiers, target new platforms, and OS by extending and modifying code derived from the Eclipse project. WebSphere Studio Workbench must be integrated and distributed as originally supplied by IBM.
Branding
Eclipse technology is not centrally branded. How component brand, it can be accepted by community members upon release compatible products. WebSphere Studio Workbench includes its own individual branding, partner programs and support offerings.
When should you choose Eclipse and when should you choose WebSphere Studio Workbench?
To help toolmakers choose which technology to use, they need to answer a few simple questions:
Determine Supported work environment tool:
- If it's WebSphere only, you should select WebSphere Studio Workbench.
- Other environments or extensions for future technologies? You should choose the Eclipse platform.
- Both environments. The choice should be made after assessing the extent of collaboration between IBM and IBM partner programs.
Will you maintain the entire offering, both Eclipse code and your own?
- If not, then WebSphere Studio Workbench is more suitable for you.
Do you provide tools for platforms not supported by IBM?
- If yes, then you should choose the Eclipse platform.
- If not, then the choice should be made based on the two previous criteria.
Would you like to have official support and participation in available affiliate programs IBM.
- If yes, then you should choose WebSphere Studio Workbench.
- If not, then you should choose the Eclipse platform.
What is Eclipse.org?
Eclipse.org is an open community-based consortium of software development tool vendors. The community is interested in working together to improve development environments and product integration. The community shares a common interest in creating products that can easily interact with each other. different environments by using plugin technology. By collaborating and sharing key integration technology, Eclipse-compatible tool vendors can focus on their own areas of expertise and the creation of new development technologies.
What is the Eclipse platform?
The core idea of the Eclipse project is to create an "Apache for developer tools." This means creating an infrastructure with open source, which provides many basic services, such as needed by developers BY. This should be a "toolkit for developing toolkits". More than just a collection of APIs, the Eclipse framework will consist of actual code written to do real work.
The Eclipse platform provides the foundation for building and running integrated end-to-end software development tools. The platform consists of open source components used by tool providers to build solutions that are built into an integrated workspace. The Eclipse platform integrates technology into a well-designed design and implementation environment.
Why is IBM releasing Eclipse as open source?
Open source is the only way to provide an open platform for tool integration. In addition, there are other benefits to using open source.
Chief among these benefits is the reuse of products. Why rebuild something if it already exists in a working format? Using the open Eclipse platform, tool creators can focus on their own development areas by providing a tooling infrastructure for building integrated development environments (IDEs). Regardless, using someone else's code starts to gain trust.
Trust in any new architecture or platform takes a long time to gain. For example, it is difficult to gain the trust of developers in creating tools that contain proprietary interfaces that limit the use of the application in a particular operating system (for example, Windows). Additionally, it is difficult to gain the trust of tool creators when different levels of APIs come with at different levels tools (for example, community APIs that differ from enterprise APIs).
The Eclipse platform builds trust by providing the platform source code.
Open source is provided for all APIs, with no internal, proprietary or hidden interfaces. Developers whose trust takes time to gain can see the code and draw appropriate conclusions. Trust the source and innovate!
Bringing together open source developers can also help create better code. When collaborating on code, creators put extra effort into it. Such code becomes a reflection of their work, the product of individual and corporate reputation. Trust the sources and establish your position in the market!
An open source project based on clean specifications can provide code that is easier to understand. An interface describes (in black box terms) the abstract behavior of a component. By examining the source code, developers can analyze the action of the code line by line. It's hard to trust someone else's interface. Trust the sources and explore the technology!
It's easier to debug in open source. When a bug is found, viewing the source code will help speed up the identification of its cause. This could be your fault, or a platform and environment fault. Access to the source code eliminates the work of guessing the cause of the error. Discussing problems together on forums allows you to share notes with others who are familiar with similar problems. If the problem occurs in commonly used open source code, it is easier to fix or work around it. Rely on the sources to get the information you need.
Working on complex technology alone is quite difficult. Multiple tool makers can take it upon themselves to explore together new technology. Trust the sources to reduce risk!
Tool suppliers come and go. Enterprise developers want to be sure of long-term platform support. If the source code is available, corporations can short term get started and maintain your business over the long term: Trust the sources to grow your business!
Flexibility is the main feature of Eclipse. With the Eclipse platform, an unsatisfactory component can be modified to suit your needs. For example, if you are not satisfied with the editor, create your own or connect one of the popular editors created in the open source marketplace offered by the Eclipse platform. Looking to tie a new hosting platform into your existing end-to-end support? Trust the sources and create plugins!
So, open source, open community and open platform set equal conditions tool creators small and large need to support end-to-end development projects and explore new frontiers.
Still not sure? Thanks to Frank Hecker for his excellent work in creating an open source store (see link in Resources).
What platforms is Eclipse available on?
Eclipse has been implemented and tested for Windows NT, Windows XP (Beta), Windows 2000, Windows 98, Windows ME, and Red Hat Linux Version 7.1. Eclipse technology was written in Java, making it easy to use on a wide range of different platforms.
Will Eclipse be ported to other platforms?
This is an issue to be resolved, but that is the beauty of the Eclipse platform. Tool creators can adopt Eclipse technology and explore the boundaries of new possibilities with the confidence of an industry-proven platform of open tools.
What is the cost of the Eclipse platform?
The Eclipse platform is available under the Common Public License. License details are listed at http://www.eclipse.org.
What about the fact that tool developers don't really want to deal with the source code and can't get much benefit from it?
Access to source code often allows problems to be quickly identified, eliminates double work, and speeds completion of new compatible technology.
Will this end up splitting the product into incompatible versions?
The Eclipse community has the right to define and approve "official" versions of the Eclipse platform. Community members can also make changes and additions for their own needs. However, the code bases vary, and creating a custom version outside of the Eclipse project becomes increasingly difficult. The costs of transferring improvements from the “official” version to it also increase. Thus, all members of the Eclipse community are interested in working together on the common core Eclipse technology and infrastructure.
Will steps be taken to define the "official" version in shipped products (for example, as part of a brand like "Eclipse Inside")?
This issue is being considered by the Eclipse Board of Directors.
What is the consumer risk when using custom versions?
Typically, the "official" version of the Eclipse platform, after testing and review, is posted on www.eclipse.org. This version is supported through Eclipse.org. Custom versions must be fully supported by the vendor, so the benefits gained from collaboration with community members are lost.
Will tool creators be concerned about open source Eclipse technology "tainting" other code if they use it in their own projects?
Eclipse is licensed under the Common Programming License, which prevents you from corrupting other code that calls Eclipse code using public APIs.
What about annoying things that users might find in Eclipse source code, such as bugs?
Open source development increases the chances of finding and fixing both minor and major bugs. They are discovered and fixed by the original developer or community members.
Could disclosing source code reveal confidential plans and strategies to competitors?
Yes, essentially we share strategies with our competitors. There is undoubtedly a more significant opinion. Developers are tired of integrating tools only into their applications. They're tired of spending time figuring out how to make tools work together in an end-to-end computing environment. With the Eclipse platform, everyone can benefit from a thorough understanding of how to integrate an IDE at a production level. We do this solely to make the end developer's job easier.
Can users simply use the Eclipse source code and rely on community members for support without adequate return?
Potentially yes, however, sooner or later the ability to interact will provide more value to the end user than using it on its own could provide. Independent isolated developers will gradually fade into oblivion.
What if competitors try to “steal” an open source product for their own purposes?
Such an attempt is possible, but the community is protected by the Common Public License. Official versions of the Eclipse platform will continue to be released in the future. The license is structured so that no supplier will be able to illegally benefit from the use of the product. By working together on the Eclipse project, we want to help achieve a meaningful level playing field for tool developers.
Where can I find information about integrating tools into Eclipse technology?
There are several technical descriptions on the website http://www.eclipse.org.
How does the Eclipse platform work and what features does it offer?
The Eclipse platform was built on the following principles:
