Bug 1066512 - RHEL6 RPMs: Upgrade jboss-remote-naming to 1.0.8.Final-redhat-1
Summary: RHEL6 RPMs: Upgrade jboss-remote-naming to 1.0.8.Final-redhat-1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: RPMs
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: EAP 6.2.2
Assignee: Vladimir Dosoudil
QA Contact: Katerina Odabasi
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-18 14:52 UTC by Fernando Nasser
Modified: 2015-02-20 11:17 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-31 16:59:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1053427 0 unspecified CLOSED [GSS] (6.2.x) Upgrade jboss-remote-naming 1.0.7.Final-redhat-1 to 1.0.8.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2014:0344 0 normal SHIPPED_LIVE Moderate: Red Hat JBoss Enterprise Application Platform 6.2.2 update 2014-03-31 20:58:30 UTC

Internal Links: 1053427

Description Fernando Nasser 2014-02-18 14:52:24 UTC 
Required upgrade.
Comment 1 Dustin Kut Moy Cheung 2014-02-19 14:42:51 UTC 
Mead build: org.jboss-jboss-remote-naming-1.0.8.Final_redhat_1-1 
Brew build: jboss-remote-naming-1.0.8-1.Final_redhat_1.1.ep6.el6
Git URL:    git://git.app.eng.bos.redhat.com/jbossas/jboss-remote-naming.git#432ffa1c30259307eb0d51850c45d18b49a4053e
Comment 3 Pavel Janousek 2014-03-25 11:59:19 UTC 
Verified during EAP-6.2.2.CP-CR3 testing cycle, included.
Comment 5 errata-xmlrpc 2014-03-31 16:59:56 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.

http://rhn.redhat.com/errata/RHSA-2014-0344.html
Note You need to log in before you can comment on or make changes to this bug.