11.3.1 Specifying a Java manifest file for Eclipse Help
By default, Mif2Go includes a Java manifest file, MANIFEST.MF. To omit this file and use only plugin.xml as a manifest:
; UseManifest = Yes (default, required for .jars) or No
If you intend to package your Eclipse Help files in a .jar file, you must keep the default value: UseManifest=Yes.
If you intend to package your Eclipse Help files in doc.zip, set UseManifest=No.
When UseManifest=Yes, Mif2Go does the following:
• Places title, ID, provider, and product-version properties in MANIFEST.MF. When UseManifest=No, these properties are included in plugin.xml instead; see §11.3.2 Specifying Eclipse Help plug-in properties.
• Includes a processing instruction in plugin.xml, and sets the plug-in schema version to 3.2 unless you specify a different version; see §11.3.4.2 Including a processing instruction to validate plugin.xml. When UseManifest=No, the processing instruction is not included in plugin.xml.
• Creates a subfolder named META-INF in your Eclipse Help project assembly folder, and moves MANIFEST.MF into META-INF; see §33.4.1 Specifying an assembly folder. When UseManifest=No, subfolder META-INF is not created.
> 11 Generating Eclipse Help > 11.3 Configuring Eclipse Help manifest files > 11.3.1 Specifying a Java manifest file for Eclipse Help