Bug 1071479 - [GSS] (6.2.x) Upgrade log4j-jboss-logmanager changed from 1.0.2.Final-redhat-1 to 1.1.0.Final
Summary: [GSS] (6.2.x) Upgrade log4j-jboss-logmanager changed from 1.0.2.Final-redhat-...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.2.3
Assignee: Vaclav Tunka
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On: 1059857 1070453 1087630
Blocks: eap62-cp03-blockers
TreeView+ depends on / blocked
 
Reported: 2014-02-28 22:17 UTC by Kyle Lape
Modified: 2018-12-05 17:29 UTC (History)
10 users (show)

Fixed In Version:
Clone Of: 1059857
Environment:
Last Closed: 2014-06-09 12:48:13 UTC
Type: Component Upgrade
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1088638 0 unspecified CLOSED RHEL6 RPMs: Upgrade log4j-jboss-logmanager to 1.1.0.Final-redhat-2 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1088639 0 unspecified CLOSED RHEL5 RPMs: Upgrade log4j-jboss-logmanager to 1.1.0.Final-redhat-2 2021-02-22 00:41:40 UTC

Internal Links: 1088638 1088639

Comment 8 Chao Wang 2014-04-16 09:42:32 UTC 
PR for productized version: https://github.com/jbossas/jboss-eap/pull/1242
Comment 10 Nikoleta Hlavickova 2014-05-05 12:09:24 UTC 
Verified with EAP 6.2.3.CP.CR2
Note You need to log in before you can comment on or make changes to this bug.