Gld Extension Development: Difference between revisions
Line 10: | Line 10: | ||
<pre> | <pre> | ||
cdgldjdg7 | |||
</pre> | </pre> | ||
Revision as of 15:14, 11 January 2017
Internal
Overview
Extensions are developed independently of the core, which include API and the load driver. Once a new core version has been released, the extensions that wish to use it should update their <gld.api.version>...</gld.api.version> in the topmost POM.
To get to the work area of an extension (jboss-datagrid-7 in this case):
cdgldjdg7
cd projects/gld/extensions/<extension-name> release snapshot
The above will build the extension and install it in ${RUNTIME_DIR}/gld/extensions. The location of the installation directory can be configured in <extension-name>/.nort/project.yaml, as "install/installation.directory".
Extension Name
The extension name, as described by the "gld Concepts - Extension Name" section, must be specified as the "extension.name" property in the extension project POM:
<project ...> ... <properties> <extension.name>jboss-datagrid-7</extension.name> ... </properties> ... </project>
The POM "extension.name" property is the authoritative source of information for extension name, and it will be inferred from it everywhere extension name is necessary.
For simplicity, it is recommended that the extension top-level directory of the extension project has the same name as "extension.name".
Extension Version
Use a variant of the procedure described here Nova Ordis Utilities Version Metadata Handling, with the difference that the resource file has an extension-specific name (example: "jboss-datagrid-7-extension-version") and call VersionUtilities.getVersion(<extension-specific-resource-file-name>) instead.