Hi All,
I need help in understanding the purpose of having vmoapp file format. I understand the dar format, but most of the plugins that I see on vmware site are of vmoapp extension.
What is the purpose of having vmoapp extension when we are already having dar file which is recognized by vco configuration api.
Are there any extra features that vsoapp packaging structure provides?
I see there contents in vsoapp:-
1. META-INF/MANIFEST.MF:-
What are all possible headers we can use in MANIFEST.MF file. Are there any mandatory Headers that must be specified for VCO to consider this vmoapp extension?
Is there any other file/information can be put in META-INF folder?
Content of Manifest file of o11nplugin-amqp-1.0.2-219.vmoapp file is given below:-
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.7.1
Created-By: 20.1-b02 (Sun Microsystems Inc.)
App-Vendor-Short: vmware
App-Version: 1.0.2-219
Build-Date: 20120730-1045
Build-Number: 219
Built-By: hudson
Specification-Vendor: VMware, Inc.
2. VSO-INF/vsoapp.txt:-
vsoapp.txt file contains liscense information.
How does this information is being used by configuration api while installing plugin?
Is the filename vsoapp.txt is fixed or we can have liscense information in file with any name?
Is there any other file/information can be put in VSO-INF?
3. dar file:-
It this the normal dar file, or any extra infromation needs to be added in this dar file to accompay it with vsoapp packaging structure.
It will be great help if anyone could answer these questions or point me to some resource where I can find answers.
Thank you for your help.
Best Regards,
Sumit Tyagi