此内容没有您所选择的语言版本。

Chapter 1. Introduction


1.1. About Patches and Upgrades

Major Upgrades

A major upgrade or migration is required when an application is moved from one major release to another, for example, from JBoss EAP 6 to JBoss EAP 7. This type of migration is not addressed in this guide.

For instructions on how to migrate from previous releases of JBoss EAP, see the Migration Guide.

Minor Updates

JBoss EAP periodically provides point releases, which are minor updates that include bug fixes, security fixes, and new features. Minor updates are not applied via patching. If you plan to upgrade from one JBoss EAP point release to another, for example, from JBoss EAP 7.0 to JBoss EAP 7.1, code changes should not be required for applications that follow the Java EE specification and do not use any private, unsupported, or tech preview modules.

For instructions on how to upgrade from one JBoss EAP 7 point release to another, see the upgrading chapter.

Cumulative Patches

JBoss EAP also periodically provides individual or cumulative patches that contain bug and security fixes. Cumulative patches increment the minor release version by the last digit, for example from 7.0.1 to 7.0.2. These patches do not require migration and should not impact the server configuration files. The patch management system for ZIP/installer installations can also rollback the patch and server configuration.

For instructions on how to patch JBoss EAP, see the patching chapter.

1.2. Subscribing to JBoss Security Announcements

The JBoss team at Red Hat maintains a mailing list for security announcements for Red Hat JBoss Middleware products. You can subscribe to this mailing list to be notified of security-related announcements that affect JBoss EAP.

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat