12.3.3 Configuring the Java manifest file for Eclipse Help
When you package Eclipse Help in a .jar file, the .jar file must include a Java manifest, MANIFEST.MF. Mif2Go can create this file for you, and does so by default when UseManifest=Yes; see §12.3.1 Specifying a Java manifest file for Eclipse Help.
To prevent Mif2Go from creating MANIFEST.MF when UseManifest=Yes:
; WriteManifest = Yes (default, always write, even if it exists)
; or No (customized, write only if not found)
When WriteManifest=Yes, Mif2Go creates MANIFEST.MF in the project directory; if this file is already present, Mif2Go overwrites it.
When WriteManifest=No, Mif2Go creates MANIFEST.MF only if this file is not already present in the project directory; Mif2Go does not overwrite an existing MANIFEST.MF. This setting allows you to customize MANIFEST.MF outside of Mif2Go, without losing your customizations during subsequent conversions.
To specify that your plug-in must run as a singleton:
; UseSingleton = No (default) or Yes (add "; singleton:=true" after
When UseSingleton=Yes, Mif2Go adds “; singleton:=true” after the value of Bundle-SymbolicName in MANIFEST.MF.
> 12 Generating Eclipse Help > 12.3 Configuring Eclipse Help manifest files > 12.3.3 Configuring the Java manifest file for Eclipse Help