Different plugin packages for 5.1 and 5.5

Hi,

I was looking at the 5.5 sdk and notice that, if i start using the 5.5 depencides for my package it may break on the 5.1 environment.

Once you start using 5.5 APIs your plugin will no longer work correctly with VWC 5.1. You must update the pluginPackage dependency on VWC version 5.1.0 to 5.5.0 so that your plugin cannot be loaded when VWC 5.1.0 is running:

  <dependencies> <!-- dependency on the current vSphere Client version is required --> <pluginPackage id="com.vmware.vsphere.client" version="5.5.0" /> </dependencies> 

If you don't update that dependency and a user connects to a vCenter where your plugin is registered using VWC 5.1 one of three things can happen:

1. The plugin still works correctly because it is not using any API incompatible with 5.1.
2. The plugin fails to deploy and the UI is not visible to users. The server log will show the reason for the deployment error.
3. The plugin UI is visible but a Flex error or Java error occurs at runtime (worst case for the user's experience).

The registration process as a vCenter extension is still the same as with version 5.1.

Can anyone suggest me what would be the best to handle this case?

Can we have two ExtensionClientInfo on the extension and somehow bind one with a particular VWC version?

Or have one ExtensionClientInfo but the url for that has a query string parameter or something to detect the version on the VCW? But then the VCW has to inject that parameter to the the base url that i have on the ExtensionClientInfo.

Thanks