Description of problem: If you try to apply a patch on a wrong or unexpected version of EAP 6.4, the CLI command returns with only "Patching Exception" message rather than a detailed or verbose message regarding what version was expected and what version was encountered. For example, if you try to apply CP09 on EAP 6.4.9, it returns with just "Patching Exception " rather than "Patch does not apply - expected (a.b.c.GA), but was (x.y.z.GA)" Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Take a Jboss EAP 6.4.9 or higher installation. 2.Via CLI, try to apply CP09 or any CP version lower than the actual EAP 6.4.x version Actual results: Patching Exception Expected results: JBAS016840: Patch does not apply - expected (6.4.x.GA), but was (6.4.y.GA) Additional info: A more detailed information regarding the failure would be convenient than just the Patching Exception
Exception on EAP 6.4.15 and older: patching exception Exception on EAP 6.4.16.CP.CR1: JBAS016952: The patch does not contain metadata for currently installed EAP version 6.4.16.GA Verified with EAP 6.4.16.CP.CR1
Released on June 20 2017 as part of the EAP 6.4.16 maintenance release.