Loading...

XML

Word

Printable

Type: Component Upgrade
Resolution: Done
Priority: Major
Fix Version/s: 27.0.0.Beta1, 27.0.0.Final
Affects Version/s: None
Component/s: None
Labels:
None

[QE] How to address?:
---
[QE] Why QE missed?:
---

Upgrade WildFly Naming Client to 1.0.16.Final, incorporates interoperability work ~~WFNC-70~~

https://github.com/wildfly/wildfly-naming-client/compare/1.0.15.Final...1.0.16.Final

incorporates

WFNC-70 Adapt wildfly-naming-client to work correctly in EAP7<->EAP8 invocation scenarios

Resolved

is cloned by

WFLY-17034 Upgrade WildFly HTTP Client to 1.1.14.Final

Closed

is depended on by

WFLY-16296 WildFly server based on Jakarta EE API should communicate successfully with previous versions of the server based on Java EE

Closed

is related to

JBEAP-24031 [GSS](7.4.z) Upgrade wildfly-naming-client from 1.0.14.Final-redhat-00001 to 1.0.15.Final-redhat-00002

Closed

Assignee:: Flavia Rainone

Reporter:: Flavia Rainone

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2022/09/21 4:23 PM

Updated:: 2023/01/04 11:37 PM

Resolved:: 2022/09/23 4:40 PM