To avoid compatibility
issues in case your plug-in package depends on other plug-in packages with
specific versions, make sure that you define correctly the plug-in dependencies
by using the
match parameter of the
dependencies element in your
plugin-package.xml
manifest file. You must specify not only the minimum required plug-in package
version compatible with your plug-in, but also the maximum one. Otherwise,
after the
vSphere Web
Client deploys your plug-in package, the plug-in will not work
because the plug-in dependencies cannot be resolved and may cause errors in the
vSphere Web
Client.
For example, you can use the
following lines in the manifest file of your plug-in package to define the
minimum and maximum supported versions of the
vSphere Web
Client:
...
<dependencies>
<pluginPackage id="com.vmware.vsphere.client" version="5.5.0" match=“greaterOrEqual" />
<pluginPackage id="com.vmware.vsphere.client" version=“6.0.0" match=“lessThan" />
</dependencies>
...
Note
If your plug-in package is
only compatible with a specific version of the
vSphere Web
Client, you must use the
equal value of the
match attribute to specify the version. In this
way, you ensure that when you upgrade the
vSphere Web
Client, your plug-in package is not deployed, and does not cause
any errors.
|