Bug 1088638 - RHEL6 RPMs: Upgrade log4j-jboss-logmanager to 1.1.0.Final-redhat-2
Summary: RHEL6 RPMs: Upgrade log4j-jboss-logmanager to 1.1.0.Final-redhat-2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: RPMs
Version: 6.2.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.2.3
Assignee: Yong Yang
QA Contact: Katerina Odabasi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-16 22:19 UTC by Fernando Nasser
Modified: 2017-10-10 00:07 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-05-27 23:51:55 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1071479 0 unspecified CLOSED [GSS] (6.2.x) Upgrade log4j-jboss-logmanager changed from 1.0.2.Final-redhat-1 to 1.1.0.Final 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2014:0563 0 normal SHIPPED_LIVE Low: Red Hat JBoss Enterprise Application Platform 6.2.3 update 2014-05-28 03:50:02 UTC

Internal Links: 1071479

Description Fernando Nasser 2014-04-16 22:19:56 UTC 
Required upgrade.
Comment 1 Fernando Nasser 2014-04-16 22:23:20 UTC 
Source URL: git://git.app.eng.bos.redhat.com/jboss-logging/log4j-jboss-logmanager.git#804ec9de5f930c01ab0bb654ba3c6bc734844697
Mead-Build: org.jboss.logmanager-log4j-jboss-logmanager-1.1.0.Final_redhat_2-1
Brew-Build: log4j-jboss-logmanager-1.1.0-2.Final_redhat_2.1.ep6.el6
Comment 2 Fernando Nasser 2014-04-16 22:24:31 UTC 
Source URL: git://git.app.eng.bos.redhat.com/jboss-logging/log4j-jboss-logmanager.git#804ec9de5f930c01ab0bb654ba3c6bc734844697
Mead-Build: org.jboss.logmanager-log4j-jboss-logmanager-1.1.0.Final_redhat_2-1
Brew-Build: log4j-jboss-logmanager-1.1.0-2.Final_redhat_2.1.ep6.el6
Comment 4 Pavel Janousek 2014-05-21 12:40:12 UTC 
Verified in CR3 build.
Comment 6 errata-xmlrpc 2014-05-27 23:51:55 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-0563.html
Note You need to log in before you can comment on or make changes to this bug.