Bug 1087606 - [GSS] (6.3.1) Upgrade jboss-remote-naming 1.0.8.Final-redhat-1 to 1.0.9.Final-redhat-1
Summary: [GSS] (6.3.1) Upgrade jboss-remote-naming 1.0.8.Final-redhat-1 to 1.0.9.Final...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Naming
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR1
: EAP 6.3.1
Assignee: Vaclav Tunka
QA Contact:
URL:
Whiteboard:
Depends On: 1069591 1131628
Blocks: eap631-blockers, eap631-payload, eap63-cp01-blockers
TreeView+ depends on / blocked
 
Reported: 2014-04-14 19:18 UTC by Brad Maxwell
Modified: 2019-05-20 11:09 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1131628 (view as bug list)
Environment:
Last Closed: 2014-10-13 18:38:19 UTC
Type: Component Upgrade
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1132811 0 unspecified CLOSED RHEL6 RPMs: Upgrade jboss-remote-naming to 1.0.9.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1132812 0 unspecified CLOSED RHEL5 RPMs: Upgrade jboss-remote-naming to 1.0.9.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1132813 0 unspecified CLOSED RHEL7 RPMs: Upgrade jboss-remote-naming to 1.0.9.Final-redhat-1 2021-02-22 00:41:40 UTC

Internal Links: 1132811 1132812 1132813

Description Brad Maxwell 2014-04-14 19:18:24 UTC 
Upgrade jboss-remote-naming 1.0.8.Final-redhat-1 to 1.0.9.Final-redhat-1 to resolve the linked issues
Comment 4 Vladimir Dosoudil 2014-08-25 05:53:39 UTC 
MEAD build: https://brewweb.devel.redhat.com/buildinfo?buildID=379672
RPM6 wrapper: https://brewweb.devel.redhat.com/buildinfo?buildID=379673
RPM5 wrapper: https://brewweb.devel.redhat.com/buildinfo?buildID=379674
RPM7 wrapper: https://brewweb.devel.redhat.com/buildinfo?buildID=379675

Prod rebuild PR: https://github.com/jbossas/jboss-eap/pull/1623
Comment 6 Jan Martiska 2014-08-29 07:37:18 UTC 
Verified in 6.3.1.CR1.
Note You need to log in before you can comment on or make changes to this bug.