Plug-in structure

Plug-ins come in two forms. One is to store the plug-in in the form of a JAR package file. This type of plug-in can be used directly with other dependent packages in the project class path. The other is to store the plug-in class file and the plug-in. Dependent packages and other resources are placed under the plug-in directory structure. Such plug-ins can be placed outside the project path and can be shared by multiple modules. The directory structure is as follows:

<PLUGIN_HOME>\
    |--.plugin\
    |   |--lib\
    |   |   |--xxxx.jar
    |   |   |--...
    |   |--classes\
    |   |   |--...
    |   |--...
    |--<plugin_xxx>\
    |   |--lib\
    |   |   |--xxxx.jar
    |   |   |--...
    |   |--classes\
    |   |   |--...
    |   |--...
    |--<plugin_xxxx>\
    |--...

Plug-in directory structure description:

• Under the PLUGIN_HOME root path specified by each plug-in factory, some JAR packages or classes can be stored in a directory named ".plugin" and other resource files for global sharing;

• Each plug-in is an independent directory, generally named after the plug-in ID (not limited to), and the plug-in related JAR packages and class files, etc. Resources are placed in the corresponding lib, classes or other directories;