A plugin normally consists of a number of files (xml, json, …). When plugins evolve files are changed over time. For it to work a plugin should use files that are built for one release; it must be avoided to mix files from different releases of the same plugin. Is there a mechanism in vera to check this?
For example, at startup of a plugin one could compute a hash over all plugin files and compare this with a stored value. However, this would be very inflexible as, for example, different distributions of the same S_* file could have the same semantic but different checksums.
Anyone thought about it? Is it already solved? Is it not a problem and its just me mixing up files by accident?
No formal validation mechanism at the moment, but in UI5 these plugins are effectively uploaded into the catalog (basically another SVN like instance), approved, and then published via apps.mios.com.
Things downloaded/installed via this mechanism should be more complete… As long as there are no ‘manual only’ install instructions (aka move this file to some very specific location etc)
What happens if my app is not approved? Can I still write my own plugins just for myself (i.e. is there still a way in UI5 to upload plugins manually?)