Understanding the Manifest

Apple Intelligence深度解析:系统级生成式AI的端云协同架构 生成式人工智能(GenAI)正从应用层功能演进为操作系统核心能力。理解其底层原理,需回归‘意图识别—任务调度—安全执行’的技术主线:苹果通过Intent Understanding Engine实现毫秒级语义解析,依托On-Device Synthesis Core与Private Cloud Compute构建分级推理体系,在保障隐私与实时性的前提下,让AI能力自然融入文本润色、跨App协同等高频场景。这种系统级集成并非简单调用大模型,而是以芯片微架构优化(如Sparse Attention Unit)、 阅读详情

Understanding the Manifest

JAR files can support a wide range of functionality, including electronic signing, version control, package sealing, extensions, and others. What gives JAR files the ability to be so versatile? The answer is embodied in the JAR file's manifest.

The manifest is a special file that can contain information about the files packaged in a JAR file. By tailoring this "meta" information that the manifest contains, you enable the JAR file to be used for a variety of purposes.

Before looking at some of the ways manifests can be modified to enable special JAR-file functionality, let's take a look at the baseline default manifest.

The Default Manifest

When you create a JAR file, it automatically receives a default manifest file. There can be only one manifest file in an archive, and it always has the pathname
META-INF/MANIFEST.MF

When a JAR file is created with version 1.2 of the JavaTM Development Kit, the default manifest file is very simple. Here are its full contents:

Manifest-Version: 1.0

This line shows that a manifest's entries take the form of "header: 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 what use you intend 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.

The format of the default manifest file changed between versions 1.1 and 1.2 of the Java Development Kit. If you create a JAR file for the java.math package, for example, the JDKTM 1.1 default manifest file would look something like this:

Manifest-Version: 1.0

Name: java/math/BigDecimal.class
SHA1-Digest: TD1GZt8G11dXY2p4olSZPc5Rj64=
MD5-Digest: z6z8xPj2AW/Q9AkRSPF0cg==

Name: java/math/BigInteger.class
SHA1-Digest: oBmrvIkBnSxdNZzPh5iLyF0S+bE=
MD5-Digest: wFymhDKjNreNZ4AzDWWg1Q==

Like the JDK 1.2 manifest file, the JDK 1.1 manifest has an entry for Manifest-Version. The version number is the same, indicating that the manifest specification didn't change between versions 1.1 and 1.2 of the JDK software.

Unlike the JDK 1.2 manifest file, the JDK 1.1 manifest has entries for each file contained in the archive, including the files' pathnames and digest values. The pathnames are given as values of the Name header. Any headers that immediately follow a Name header without any intervening blank lines, pertain to the file specified by the Name header. In the manifest above, for example, the first Name header is followed by these lines:

SHA1-Digest: TD1GZt8G11dXY2p4olSZPc5Rj64=
MD5-Digest: z6z8xPj2AW/Q9AkRSPF0cg==
Because these lines follow the Name header without any intervening blank lines, you know that the digest values they specify are the digest values for the file java/math/BigDecimal.class.

Digest values are relevant only with respect to signing JAR files. In fact, that's why the digest information isn't in the JDK 1.2 default manifest -- it isn't always needed. To learn more about digests and signing, see the Signing and Authenticating JAR Files lesson.

Special-Purpose Manifest Headers

Depending on what role you want your JAR file to play, you may need to modify the default manifest. If you're interested only in the "ZIP-like" features of JAR files such as compression and archiving, you don't have to worry about the manifest file. The manifest doesn't really play a role in those situations.

Most uses of JAR files beyond simple archiving and compression 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 - version 1.2 only
If you have an application bundled in a JAR file, you need some way to indicate which class within the JAR file is your application's entry point. (Recall that the entry point is the class having a method with signature public static void main(String[] args).)

You provide this information with the Main-Class header, which has the general form:

Main-Class: classname
The value classname is the name of the class that is your application's entry point.

Download Extensions - version 1.2 only
Download extensions are JAR files that are referenced by the manifest files of other JAR files. See the trail on the extension mechanism for information about extensions.

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. <!--

Hiding Implementation Classes in JAR Files - version 1.2 only
Your JAR file may contain packages that are part of your software's implementation that aren't intended to be publically visible to other applications. You can hide such packages by using the Exported-Packages header. When this header is used, only those packages listed as the header's value will be visible outside the JAR file. For example:

Exported-Packages: com.ourcom.* com.mycom
specifies that the package com.mycom and all packages with names beginning with com.ourcom will be visible outside the JAR file. All other packages in the JAR file will be hidden.

If the manifest doesn't have an Exported-Packages header, all packages are visible. -->

Package Sealing - version 1.2 only
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. You might want to seal a package, for example, to ensure version consistency among the classes in your software or as a security measure.

To seal a package, you need to add a Name header 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 - version 1.2 only
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."

Additional Information

A specification of the manifest format is part of the on-line JDK documentation.
Unity打包PICO4 APK全攻略:从环境配置到疑难报错解决方案 在移动应用与XR开发领域,APK打包是将项目部署到Android设备的关键环节,其本质是构建系统对代码、资源与平台SDK的集成与编译过程。理解Gradle构建原理、IL2CPP编译机制以及Android Manifest的合并规则,对于解决跨平台兼容性问题至关重要。这些技术能确保应用性能优化、资源管理得当,并实现稳定的运行时环境。在VR/AR开发场景中,针对PICO4等XR设备进行打包时,常需处理特定的SDK集成、权限配置与图形API适配。本文聚焦Unity引擎下PICO4 APK打包的常见问题,通过分析G 阅读详情

相关推荐

Claude for Chrome:AI驱动的浏览器自动化新范式

浏览器自动化正从传统RPA的DOM定位与坐标依赖,转向以视觉理解、自然语言控制和权限栅栏为核心的智能代理模式。AI-powered browser assistance 通过实时截图分析UI布局、识别按钮与表单元素,结合意图解析模型将用户指令映射为可执行动作;其技术价值在于降低操作复杂度、提升跨网页任务可控性,并在邮件归档、表单填充等高频办公场景中释放人力。区别于黑盒式全自动工具,它强调基于权限的动作审批与网站粒度白名单管理,兼顾效率与安全。本文深入解析 Claude for Chrome 的设计逻辑、实操

liudaoru - 悟 464

CMake Error at G:~/cmake/build.cmake:552 (message): ERROR: The “path“ field in the manifest file

错误发生在“idf_component.yml”文件中的 “protocol_examples_tapif_io”和“protocol_examples_common” 组件的路径跟实际idf安装位置不一致。因为项目需要从idf安装文件里获取组件,由于我idf安装位置发生了变化,导致路径失效,CMake无法找到目录。将“idf_component.yml”文件中的地址修改即可。在使用SDK配置编辑器时发生如下错误。VScode、ESP-idf组件。

m0_61689711的博客 1530

AudioTrack音频播放流程深度解析

深入解析Android AudioTrack音频播放的完整链路:从Java API到Native层,从共享内存Ring Buffer机制到FAST Track低延迟优化,配合源码分析带你彻底搞懂Android音频播放的底层原理

Cheson的专栏 942

eclipse打jar包产生的问题

方案一:用Eclipse自带的Export功能 步骤1:准备主清单文件 “MANIFEST.MF”, 由于是打包引用了第三方jar包的Java项目,故需要自定义配置文件MANIFEST.MF,在该项目下建立文件MANIFEST.MF,内容如下: Manifest-Version: 1.0 Class-Path: lib/commons-codec.jar lib/commons-

人生最遗憾的莫过于:轻易地放弃了不该放弃的,固执地坚持了不该坚持的 1179

【PCL】SolidWorks 三维建模 STL, OBJ 采样生成 PCD 点云数据(附源码)

[PCL自学篇] 一.SolidWorks三维建模STL,OBJ采样生成PCD点云数据新的改变功能快捷键合理的创建标题,有助于目录的生成如何改变文本的样式插入链接与图片如何插入一段漂亮的代码片生成一个适合你的列表创建一个表格设定内容居中、居左、居右SmartyPants创建一个自定义列表如何创建一个注脚注释也是必不可少的KaTeX数学公式新的甘特图功能,丰富你的文章UML 图表FLowchart流程图导出与导入导出导入 这阵子做线结构光视觉检测(轨道)项目的过程中,发现之前的许多知识点在逐渐遗忘,常言好记性

idiot5lie的博客 1万+

VScode远程连接开发嵌入式开发板

VScode远程连接开发调试嵌入式开发板

qq_53221728的博客 5893

Understanding the Manifest (转)

Understanding the Manifest (转)[@more@]Understanding the Manifest JAR files can support a wide range of functio...

csd3176的博客 181

医疗设备安规入门:一张图搞懂BF型设备的MOOP/MOPP绝缘路径(附GB 9706.1附录解析)

本文深入解析了BF型医疗设备的MOOP/MOPP绝缘路径设计,结合GB 9706.1标准附录J的实战应用,帮助工程师快速掌握医疗设备安规要点。通过典型绝缘路径图分析,详细对比了MOOP与MOPP的防护差异,并提供了海拔修正、漏电流测试等关键设计指南,助力医疗设备安全合规。

weixin_30633405的博客 394

Understanding the MANIFEST.MF

[url]http://java.sun.com/docs/books/tutorial/deployment/jar/defman.html[/url] [b]pathname[/b] META-INF/MANIFEST.MF [b]only one manifest file in an archive[/b] [b]form of "header: value" pair...

iteye_4020的博客 195

海思MIPI屏调试实战:从参数计算到点亮屏幕的完整指南

本文提供了一份海思平台MIPI屏幕调试的完整实战指南。文章以Hi3516DV300调试800x1280分辨率屏幕为例,详细讲解了从参数计算、配置文件修改到最终点亮屏幕的全流程,并分享了常见问题排查与进阶优化技巧,旨在帮助嵌入式开发者高效解决MIPI屏调试难题。

weixin_29190573的博客 740

【Network Management】DCM模块唤醒网络是主动唤醒还是被动唤醒

DCM模块唤醒网络是主动唤醒还是被动唤醒

qq_36056498的博客 1542

simple understanding of manifest

why manifest file exist? An assembly manifest is an XML file that describes a side-by-side assembly. Assembly manifests describe the names and versions of side-by-side assemblies, files, and resour

小文panda的专栏 687

Open3D (C++) 计算点云坐标最值及其索引

使用C++版本的Open3D计算点云最值点及其对应的下标索引

点云侠的博客 731

Understanding PWA

原文地址: https://blog.webkong.cn/2018/... What is pwa? Progressive Web App, 简称 PWA,是提升 Web App 的体验的一种新方法,能给用户原生应用的体验。 PWA 能做到原生应用的体验不是靠特指某一项技术,而是经过应用一些新技术进行改进,在安全、性能和体验三个方面...

weixin_34040079的博客 245

SpringBoot+Vue+kkFileView实现文档管理(文档上传、下载、在线预览)

上面在使用OpenOffice实现doc、excel、ppt等文档的管理和预览。除此之外可用kkFileView实现包括且更多文档的预览。

BADAO_LIUMANG_QIZHI的博客 1万+

廖雪峰Python教程[完整版]

廖雪峰的python教程整理的,已经排好版了,而且还是完整的,适合小白

终极文档转换革命:如何用markitdown统一处理30+文件格式为LLM友好Markdown

在当今AI驱动的世界中,文档处理已成为每个开发者和数据科学家必须面对的挑战。PDF、Word、Excel、PPT、EPUB、HTML、图片、音频……格式五花八门,而大语言模型却只"理解"Markdown。markitdown正是解决这一痛点的终极工具,它能将30多种文件格式统一转换为LLM友好的Markdown格式,为AI应用提供标准化的文本输入。 ## 文档格式碎片化:AI时代的最大障碍 你

gitblog_01059的博客 473

visio安装包

Microsoft Office Visio 是一款专业的制图软件。利用经过更新的形状、协作工具和数据链接图表,创建专业级图表以简化复杂的信息。

Home Assistant core:raise-pull-request Agent 的 11 步 PR 自动化工作流全解析

本文以 [raise-pull-request Agent 定义文件](https://link.gitcode.com/i/76d399d33676dcb026201a1095727c0e) 为主体,完整拆解该 Agent 在 Home Assistant core 仓库中创建 Pull Request 的 11 个步骤:从基线分支确定、代码质量检查、集成测试,到 PR 标题撰写、变更类型判定与

gitblog_00552的博客 748

VC中sqlite的使用

在VC中对sqlite的使用,实现数据库大批数据的快速插入,读取数据库中的数据在ListCtrl中显示

华为的C语言编程规范.pdf

华为技术有限公司内部技术规范。本规范制定了编写C语言程序的基本原则、规则和建议。从代码的清晰、简洁、可测试、安全、程序效率、可移植各个方面对C语言编程作出了具体指导。

考研英语单词20

optimistic a.乐观主义的(negative 悲观的,被动的 pessimistic a.悲观的,厌世的)【optimisim n.乐观主义 optimist n.乐观者 pessimism n.悲观主义。evident a.明显的,显然的【evidently ad.明显地 self-evdient a.不言而喻的 evidence n.证据,迹象 in evidence 明显的,可看见的】fierce a.凶猛的,狂热的【fiercely ad.凶猛地】

weixin_63566653的博客 656

OpenAI无屏智能音箱AI伴侣技术解析与开发实战

智能语音助手作为人工智能的重要应用领域,其技术原理基于自然语言处理和语音识别技术。通过深度学习模型实现语音到文本的转换和语义理解,技术价值在于提供更自然的人机交互体验。在应用场景方面,智能语音助手广泛应用于智能家居控制、信息查询和个性化服务等领域。OpenAI最新推出的无屏智能音箱AI伴侣,通过集成GPT系列模型的对话能力和边缘计算技术,解决了传统语音助手交互不自然和上下文记忆差等痛点。该设备采用云端协同架构,为开发者提供完整的SDK和API接口,支持智能家居控制、企业客服等多样化应用开发。

weixin_33889665的博客 379

工具Cursor(一)介绍&简单使用&特色

下载安装后使用google账户登录。使用代码库索引后:✅ AI 回答更准确,因为它能基于当前项目的索引库回答问题✅ 文件搜索更快✅ AI 能更好地理解跨文件的关系✅ 重构建议更精准实际效果对比使用代码库索引和不使用代码库索引的主要区别:使用代码库索引时,AI 先搜索了项目中的文件,然后根据文件内容回答AI 能准确指出项目中实现的具体功能和代码不使用代码库索引时,AI 只能从一般角度回答,没有针对项目的具体情况什么是 AI 规则?AI 规则是 Cursor 的一个功能。

w_t_y_y的博客 2713

CANN/hcomm HCCL-VM虚拟执行环境

HCCL-VM is a virtual execution environment for high-performance collective communication targeting Huawei Ascend NPU cards. This tool enables the development and functional verification of HCCL collec

gitblog_00459的博客 1092

零代码构建AI语音助手:NeMo Voice Agent完整实战指南

想要快速构建本地部署的智能语音助手却苦于复杂的代码编写?NeMo Voice Agent为你提供终极解决方案!这个开源框架将NVIDIA NeMo的语音识别(ASR)、文本转语音(TTS)技术与HuggingFace大语言模型(LLM)无缝集成,让你无需编写复杂代码即可搭建功能完整的智能语音交互系统。无论是智能家居控制、企业客服机器人还是多语言口语练习助手,NeMo Voice Agent都能提供

gitblog_00430的博客 317

AI文档智能:分层架构实现高精度结构化信息提取

文档智能(Document Intelligence)是将非结构化PDF、扫描件、合同等文本转化为可计算结构化数据的关键技术。其核心原理在于突破传统OCR或规则匹配的局限,依托大语言模型的语义理解能力,结合预处理切片、领域感知推理、跨文档关联与可信验证四层协同机制,实现字段级精准提取与逻辑一致性校验。该技术显著提升法务合规审查、金融尽调、医疗注册申报等场景的信息处理效率与决策可信度。本文聚焦AI Document Intelligence落地中的工程化实践,详解LLM-powered extraction如

cuankuangzhong6373的博客 381

GOTO 语句有害论 | 反对 GOTO 语句的理由

……

u013669912的博客 1882
上一篇: Getting Listeners from JavaBeansTM
下一篇: Distributed Java Programming with RMI and CORBA
CanFly
博客等级 码龄25年 0粉丝 18原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值