#### 21.3.1 Specifying a Java manifest file for Eclipse Help

By default, DITA2Go includes a Java manifest file, MANIFEST.MF. To omit this file and use only plugin.xml as a manifest:

    [EclipseHelpOptions]
    ; UseManifest = Yes (default, required for .jars) or No
    UseManifest = 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, DITA2Go 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 §21.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 §21.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 subdirectory named META-INF in your Eclipse Help project wrap directory, and moves MANIFEST.MF into META-INF; see §44.6.1 Specifying a wrap directory. When UseManifest=No, subdirectory META-INF is not created.

Previous Topic: 21.3 Configuring Eclipse Help manifest files

Next Topic: 21.3.2 Specifying Eclipse Help plug-in properties

Parent Topic: 21.3 Configuring Eclipse Help manifest files

Sibling Topics:

21.3.2 Specifying Eclipse Help plug-in properties

21.3.3 Configuring the Java manifest file for Eclipse Help

21.3.4 Configuring the plug-in manifest file for Eclipse Help

Table of Contents • Index