英文:
What is diff between jdk1.7_99 and jdk1.7_271
问题
我想看一下 jdk1.7_99 和 jdk1.7_271 之间的差异。
有没有任何方法可以让我查看两者之间的差异？比如是否存在任何我必须了解的已弃用方法。如果我们将系统更新为 jdk1.7_271，会有任何问题吗？
谢谢。
编辑
从评论中我得知如何检查这些版本之间的差异。谢谢。
英文:
I want to see the diff between jdk1.7_99 and jdk1.7_271.
Is there anyway I can see the diff between two? like any deprecated method is there which I must know. If we updated our system with jdk1.7_271, will there be any problem?
Thank You.
EDIT
I got it from the comments that how to check the differences between these versions. Thank you.
答案1
得分: 1
如从此链接所述：
次要版本兼容性
与具有相同主版本号的先前次要版本进行比较时，次要版本具有以下兼容性：
- Java源代码和目标级别：相同
- 兼容的Java版本：可以添加/弃用，但不能删除版本
- 支持的Java版本：可以添加版本或删除弃用版本
- Java API：可以添加/弃用，但不能删除API
- 第三方库：可以添加/升级，但不能删除库；库的升级必须遵循Java API兼容性规则
- 配置：可以添加/弃用，但不能删除选项/属性/Beans等
- 协议消息：可以添加新的协议/选项，但不能删除；与先前次要版本共同的协议实现保持兼容
- 存储格式（API）：可以向格式中添加内容，但不能以预计会破坏与数据交互的标准工具的方式删除内容
- 存储格式（非API）：可以更改方式，使旧的次要版本无法处理数据
由此带来的结果是，从一个次要版本升级到另一个次要版本除了安装要使用的版本并更新任何使用的第三方插件的构建之外，不需要进行任何更改。
现有的配置文件将保持不变，但可能需要进行修改以利用新功能。降级到旧的次要版本可能需要删除较新版本引入的配置选项。
请注意，在添加API时，不会向现有的公共接口或类添加抽象或接口方法，以确保现有扩展的编译时兼容性。
英文:
As stated from this link:
Minor Version Compatibility
A minor version has the following compatibility when compared with a previous minor version with the same major version number:
- Java Source and Target Level: identical
- Compatible Java Versions: may add/deprecate, but not remove, versions
- Supported Java Versions: may
add versions or remove deprecated versions - Java API: may add/deprecate, but not remove, APIs
- 3rd Party Libraries: may add/upgrade, but not remove, libraries; upgrades to libraries must follow the Java API compatibility rules
- Configuration: may add/deprecate, but not remove, options/properties/beans/etc.
- Protocol Messages: may add, but not remove, new protocols/options; protocol
implementations in common with previous minor versions remain
wire-compatible - Storage Formats (API): may add to, but not remove
from, formats in ways that would not be expected to break standard
tools interacting with the data - Storage Formats (non-API): may change
in ways that render older minor versions incapable of working with
the data
The result of this is that upgrading from one minor version to another does not require any change other than installing the version to be used and updating the builds of any third-party plugins used.
Existing configuration files will work unchanged, but may need to be modified to take advantage of new features. Downgrading to an older minor version may require removing configuration options introduced in newer versions.
Note that in adding APIs, abstract or interface methods are not added to existing public interfaces or classes to guarantee compile-time compatibility for existing extensions.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论