Bug 1479811

Summary:	(6.4.z) Upgrade log4j-jboss-logmanager from 1.1.2 to 1.1.4
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Fedor Gavrilov <fgavrilo>
Component:	Build	Assignee:	Fedor Gavrilov <fgavrilo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Peter Mackay <pmackay>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.17	CC:	bmaxwell, dosoudil, msochure, pgier, pmackay, vtunka
Target Milestone:	CR4
Target Release:	EAP 6.4.17
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-06 13:33:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1467885
Bug Blocks:	1450092

Description Fedor Gavrilov 2017-08-09 12:48:38 UTC

Comment 2 Vladimir Dosoudil 2017-08-09 13:36:25 UTC

JBoss Log4j Emulation 1.1.4.Final-redhat-1

MEAD build: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=581168
RPM6 wrapper: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=581173
RPM5 wrapper: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=581178
RPM7 wrapper: https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=581180

PR: https://github.com/jbossas/jboss-eap/pull/3044

Comment 3 Peter Mackay 2017-08-28 09:10:35 UTC

Verified with EAP 6.4.17.CP.CR4

Comment 4 Petr Penicka 2017-09-06 13:33:52 UTC

Released on 2017-09-05 as part of the EAP 6.4.17 release.