Eclipse plug-in mechanism.

Eclipse is famous for its powerful plug-in mechanism. It can be said that eclipse is composed of plug-ins. In eclipse 3.0, with the rise of the RCP concept, the entire Eclipse plug-in also forms a clear hierarchy. The underlying layer is RCP Org. eclipse. core. runtime, org. eclipse. ui; a large number of plug-ins such as Org. eclipse. SWT, org. eclipse. jface, org. eclipse. platform is a dedicated function plug-in, such as CDT, jdt, and EMF. This article briefly introduces the popular plug-ins.
The first is a plug-in Hierarchy
+ Eclipse SDK
Org. Eclipse. SDK
+ Eclipse Platform
+ RCP
Org. Eclipse. Core. Runtime
Org. Eclipse. UI
Org. Eclipse. Update. Configurator
Org. Eclipse. SWT
Org. Eclipse. jface
Org. Eclipse. Platform
Org. Eclipse. Debug
Org. Eclipse. ant
Org. Eclipse. Help
...
+ Jdt
Org. Eclipse. jdt. Core
Org. Eclipse. jdt. UI
Org.eclipse.jdt.doc
Org. Eclipse. jdt. Debug
Org. Eclipse. jdt. JUnit

+ PDT
Org. Eclipse. PVDF
Org. Eclipse. PVDF. Build
Org. Eclipse. PVDF. Core
Org. Eclipse. PVDF. Runtime
Org. Eclipse. PVDF. UI
Org.eclipse.pde.doc
Org. Eclipse. PVDF. Source

As you can see, the eclipse SDK is the sum of these plug-ins. Among all these plug-ins, the core is the plug-ins of RCP, org. eclipse. core. runtime, org. eclipse. UI (theoretically, rcp should contain these two components, but according to my understanding, there is no Org. eclipse. update. configuration, org, Eclipse. SWT, org. eclipse. jface, org. eclipse. workbenchde support,
It is impossible to write RCP programs with UI ). Org. eclipse. core. runtime mainly provides cross-platform runtime support and management mechanisms for other plug-ins. eclipse. the UI provides cross-platform Interface Support. Note that org. eclipse. the UI depends on five plug-ins. Open Eclipse/plugins/org. eclipse. ui_3.0.1/plugin. XML file, you can find the following lines of text, clearly illustrate this dependency:
<Requires>
<Import plugin = "org. Eclipse. Core. RunTime"/>
<Import plugin = "org. Eclipse. Help"/>
<Import plugin = "org. Eclipse. SWT" Export = "true"/>
<Import plugin = "org. Eclipse. jface" Export = "true"/>
<Import plugin = "org. Eclipse. UI. workbench" Export = "true"/>
</Requires>.

Above RCP is the platform layer of Eclipse, which is responsible for the interface, operations, and functions of Eclipse. For example, eclipse menus, various views and editors, debugging capabilities, and help support. This layer is the largest and most complex part of Eclipse.
Here, org. eclipse. SWT, org. eclipse. jface provides underlying support for cross-platform UIS, while Org. eclipse. UI. workbench implements a part of the eclipse part of the Upper-layer UI framework, and ultimately by Org. eclipse. UI. IDE implements most of the UI components and functions such as menus, editing windows, and task lists.

Platform is the SDK layer of eclipse. It is actually Platform + jdt + PDT. On platform, eclipse truly becomes a complete development tool. At the same time, it is precisely because of this design method of eclipse that eclipse, as a development environment, can be almost unlimited expansion, not only supports Java Development, plug-in development, C ++ development, but also python, XML, Perl, UML, and so on. Go to the http://www.eclipse-plugins.info and see why I said that. Unfortunately, I cannot find plug-ins related to. NET development.

Obviously, due to the plug-in-based design of Eclipse, eclipse itself has unlimited development space and is unique in many development environments. In addition, since version 3.0, the eclipse development team has been adjusting the Eclipse plug-in organization structure to make the hierarchy of these plug-ins clearer, the concept of RCP on this basis makes it possible for many plug-ins to run independently from eclipse.