Use of the MANIFEST.MF file in Java

青旅半醒 2022-09-26 03:56 168阅读 0赞

老外们很讲究，回答两个问题的人吵起来了！所以这里会加链接。

这里是链接，这里是链接，这里是链接！

[http://stackoverflow.com/questions/12767886/use-of-the-manifest-mf-file-in-java][http_stackoverflow.com_questions_12767886_use-of-the-manifest-mf-file-in-java]

[http://docs.oracle.com/javase/tutorial/deployment/jar/sealman.html][http_docs.oracle.com_javase_tutorial_deployment_jar_sealman.html]

[https://docs.oracle.com/javase/tutorial/deployment/jar/manifestindex.html][https_docs.oracle.com_javase_tutorial_deployment_jar_manifestindex.html]

The content of the Manifest file in a JAR file created with version 1.0 of the Java Development Kit is the following.

Manifest-Version: 1.0

All the entries are as name-value pairs. The name of a header is separated from its value by a colon. The default manifest shows that it conforms to version 1.0 of the manifest specification. The manifest can also contain information about the other files that are packaged in the archive. Exactly what file information is recorded in the manifest will depend on the intended use for the JAR file. The default manifest file makes no assumptions about what information it should record about other files, so its single line contains data only about itself. Special-Purpose Manifest Headers

Depending on the intended role of the JAR file, the default manifest may have to be modified. If the JAR file is created only for the purpose of archival, then the MANIFEST.MF file is of no purpose. Most uses of JAR files go beyond simple archiving and compression and require special information to be in the manifest file. Summarized below are brief descriptions of the headers that are required for some special-purpose JAR-file functions

**Applications Bundled as JAR Files:** If an application is bundled in a JAR file, the Java Virtual Machine needs to be told what the entry point to the application is. An entry point is any class with a public static void main(String\[\] args) method. This information is provided in the Main-Class header, which has the general form:

Main-Class: classname

The value classname is to be replaced with the application's entry point.

**Download Extensions:** Download extensions are JAR files that are referenced by the manifest files of other JAR files. In a typical situation, an applet will be bundled in a JAR file whose manifest references a JAR file (or several JAR files) that will serve as an extension for the purposes of that applet. Extensions may reference each other in the same way. Download extensions are specified in the Class-Path header field in the manifest file of an applet, application, or another extension. A Class-Path header might look like this, for example:

Class-Path: servlet.jar infobus.jar acme/beans.jar

With this header, the classes in the files servlet.jar, infobus.jar, and acme/beans.jar will serve as extensions for purposes of the applet or application. The URLs in the Class-Path header are given relative to the URL of the JAR file of the applet or application.

**Package Sealing:** A package within a JAR file can be optionally sealed, which means that all classes defined in that package must be archived in the same JAR file. A package might be sealed to ensure version consistency among the classes in your software or as a security measure. To seal a package, a Name header needs to be added for the package, followed by a Sealed header, similar to this:

Name: myCompany/myPackage/ Sealed: true

The Name header's value is the package's relative pathname. Note that it ends with a '/' to distinguish it from a filename. Any headers following a Name header, without any intervening blank lines, apply to the file or package specified in the Name header. In the above example, because the Sealed header occurs after the Name: myCompany/myPackage header, with no blank lines between, the Sealed header will be interpreted as applying (only) to the package myCompany/myPackage.

**Package Versioning:** The Package Versioning specification defines several manifest headers to hold versioning information. One set of such headers can be assigned to each package. The versioning headers should appear directly beneath the Name header for the package. This example shows all the versioning headers:

Name: java/util/ Specification-Title: "Java Utility Classes" Specification-Version: "1.2" Specification-Vendor: "Sun Microsystems, Inc.". Implementation-Title: "java.util" Implementation-Version: "build57" Implementation-Vendor: "Sun Microsystems, Inc."

[http_stackoverflow.com_questions_12767886_use-of-the-manifest-mf-file-in-java]: http://stackoverflow.com/questions/12767886/use-of-the-manifest-mf-file-in-java
[http_docs.oracle.com_javase_tutorial_deployment_jar_sealman.html]: http://docs.oracle.com/javase/tutorial/deployment/jar/sealman.html
[https_docs.oracle.com_javase_tutorial_deployment_jar_manifestindex.html]: https://docs.oracle.com/javase/tutorial/deployment/jar/manifestindex.html