Plugins are distributed separately from the Galia core application and extend its functionality. Using plugins, you can add support for new:
Plugins are packaged as folders. The root level contains a README and other documentation, and there is a lib subfolder containing the plugin code, and any required dependencies, packed into JAR files. Plugins physically reside inside the core application's plugins folder.
Plugins are developed against a particular version of the Galia API, referred to as the specification version. This is different from the application version. When the tools described below (e.g. bin/install_plugin.sh) are used to install or update a plugin, they will try to obtain the latest version of the plugin that has a compatible specification version, which may not be the latest available version of the plugin, if the core version is not current.
The bin/version.sh script can be used to print the application's specification version.
Specification versions are compared semantically, where major version advances break compatibility, and minor version advances only add functionality without breaking compatibility. For example:
Application specification version | Plugin specification version | Compatible? |
---|---|---|
1.0 | 1.0 | ✓ |
1.0 | 1.1 | × |
1.1 | 1.0 | ✓ |
2.0 | 1.1 | × |
The plugins page lists all available first-party plugins.
There are two ways to install a plugin:
To verify that the plugin has been installed, run bin/list_plugins.sh
.
Afterwards, restart the application.
There are two ways to update a plugin:
To verify that the plugin has been installed, run bin/list_plugins.sh
.
Afterwards, restart the application.
There are two ways to remove a plugin:
Afterwards, restart the application.
See the documentation for the is.galia.plugin
package in the Javadoc for development information. Also, it may be helpful to review the source code of some of the existing plugins.