Bug 1691431

Summary: [GSS](6.4.z) Upgrade JBoss Remote Naming from 1.0.13 to 1.0.15
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: BuildAssignee: Tomas Hofman <thofman>
Status: CLOSED ERRATA QA Contact: Peter Mackay <pmackay>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.21CC: pgier, pmackay, thofman, vtunka
Target Milestone: CR1   
Target Release: EAP 6.4.22   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-13 17:01:24 UTC Type: Component Upgrade
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1691399    
Bug Blocks: 1613417    

Description Brad Maxwell 2019-03-21 15:15:51 UTC

Comment 2 Peter Mackay 2019-03-24 10:56:29 UTC
Was there something wrong with https://github.com/jbossas/jboss-remote-naming/commits/1.0.14.Final ?

Comment 7 Peter Mackay 2019-05-08 20:29:28 UTC
Regression tests passed
Verified with EAP 6.4.22.CP.CR1

Comment 9 errata-xmlrpc 2019-05-13 17:01:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.