Following recent feedback from many of you that there is insufficient guidance on how to write robust plug-ins and observing the amount of dependency issues reported on this forum we have extended the current Best practices guide with more OSGi-related recommendations.
In addition to that a new OSGi usage validation feature has been released with the HTML Client part of HTML Client SDK Fling 3. Upon HTML Client startup it automatically checks your plug-ins for OSGi problems (i.e. usage that does not comply with the OSGi best practices) immediately after deployment of all plug-ins.
You can view the validation results in the plugin-medic.log file which is generated alongside your vsphere_client_virgo.log. Fixing all reported warnings would eliminate many of the possible causes for dependency issues of your plug-in or clashes with other plug-ins.
For more details about all types of OSGi validation checks please have a look at the "Checking your plug-in for OSGi problems" section of the Getting_Started_with_HTML_Client_SDK_Fling.pdf document. The latest HTML samples also provide useful tips on making robust manifests.
Hope your plug-in's validation output looks like this:
[INFO ] [com.mycompany.myplugin:1.0.0] STARTED Validating [My Plug-in, My Company] [INFO ] [com.mycompany.myplugin:1.0.0] FINISHED Validating [My Plug-in, My Company]
Cheers,
Vladimir