You can validate your development environment setup by generating an HTML plug-in from the plug-in project template. Use the automation scripts provided with the SDK for building the plug-in.

To create a plug-in package from the project template, run the 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-ui folder of the project template.

After running the script, you see the plugin_name folder that contains the plugin-package.xml manifest file and the plugins folder with the WAR and JAR files generated for the UI and service components. For more information about the XML elements of the plugin-package.xml manifest file, see XML Elements of the Plug-In Package Manifest File.

Example: 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. 

<pluginPackage id="com.mycompany.myplugin" version="1.0.0" type="html" name="myplugin"
      description="Add plugin description" vendor="Add vendor">
   <dependencies>
      <pluginPackage id="com.vmware.vsphere.client" version="6.0.0" />
   </dependencies>
   <bundlesOrder>
      <bundle id="com.google.gson" />
      <bundle id="com.mycompany.myplugin.myplugin-service" />
      <bundle id="com.mycompany.myplugin.myplugin-ui" />
   </bundlesOrder>
</pluginPackage>

You can follow these recommendations for the plugin-package.xml file to ensure that your plug-in can be deployed on both Web browser applications:

■

Specify a unique plug-in package ID for the id attribute of the pluginPackage XML element.

■

Add the type="html" attribute to the pluginPackage elements. This attribute is required if you want your plug-in to be deployed on the vSphere Client.

■

Specify that your plug-in depends on the com.vmware.vsphere.client package with 6.0.0 version. This dependency ensures that your plug-in can be deployed on the vSphere Web Client 6.0.