Building a Plug-In
Package from the Project TemplateLast Updated December 16, 2024
You build an HTML
plug-in from the plug-in project template by using the automation scripts
provided with the SDK.
To build a plug-in package from
the project template, run the
folder of the project template.
build-plugin-package.bat
or the
build-plugin-package.sh
script depending on your operating system. You can locate these scripts in the
plugin_name
-uiAfter you run the script, you
see the
folder that contains the
plugin_name
plugin-package.xml
manifest file and the
plugins
folder with
the WAR and JAR files generated for the UI and service components.
Plug-In Package
Manifest File
The following example shows
the contents of the
plugin-package.xml
manifest file that is generated for the template HTML plug-in.
Follow these recommendations
for the
plugin-package.xml
file to ensure that your plug-in can be deployed on the
vSphere Client
:
- Specify a unique plug-in package ID for theidattribute of thepluginPackageXML element.
- Add thetype="html"attribute to thepluginPackageelements. This attribute is required if you want your plug-in to be deployed on thevSphere Client.
- Specify that your plug-in depends on thecom.vmware.vsphere.clientpackage and thecom.vmware.vsphere.client.htmlpackage, version6.5.0. This dependency ensures that your plug-in can be deployed on thevSphere Client6.5.
- To specify an Update release as the minimum version supported by your plug-in, you need to use a special numbering system. For example, to specify that your plug-in supports only 6.5 Update 2 or above, use the version6.5.0.20000for the dependency.