Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Blocker
Fix Version/s: 7.12.1.GA
Affects Version/s: 7.12.1.GA
Component/s: Upgrade Tool
Labels:
None

Blocked:
False
Ready:
False
Affects Build:
CR1
Fix Build:
CR2
Target Release:

7.12.1.GA
Git Pull Request:
https://github.com/jboss-integration/bxms-patch-tools/pull/203, https://github.com/jboss-integration/bxms-patch-tools/pull/204
Steps to Reproduce:

Hide

1. Install RHPAM 7.12.0 (using the installer) on top of EAP 7.4
2. Run the 7.12.1 update tool on it (for now it can be downloaded from indy https://indy.psi.redhat.com/api/content/maven/hosted/pnc-builds/org/jboss/brms-bpmsuite/patching/rhpam/7.12.1.redhat-00001/rhpam-7.12.1.redhat-00001-update.zip)

Show
1. Install RHPAM 7.12.0 (using the installer) on top of EAP 7.4 2. Run the 7.12.1 update tool on it (for now it can be downloaded from indy https://indy.psi.redhat.com/api/content/maven/hosted/pnc-builds/org/jboss/brms-bpmsuite/patching/rhpam/7.12.1.redhat-00001/rhpam-7.12.1.redhat-00001-update.zip )

SFDC Cases Counter:
SFDC Cases Links:

Description

RHPAM/RHDM changed to use EAP bootable jar starting on version 7.12.0. This change introduced some changes in the MANIFEST.MF that was used to check if the patch was valid for a distribution and version.

Said that we can't rely on the MANIFEST.MF file anymore, but we can use the build.metada instead to make this check.

Attachments

Activity

People

Assignee:: Roberto Oliveira

Reporter:: Roberto Oliveira

Tester:: Martin Cimbalek

QA Contact:: Martin Cimbalek

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: 2022/02/16 2:35 PM

Updated:: 2024/02/12 9:08 AM

Resolved:: 2022/03/09 10:21 AM