Bug 975555

Summary: Upgrade JBoss LogManager for EAP 6.1.1
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Kyle Lape <klape>
Component: LoggingAssignee: James Perkins <jperkins>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1.1CC: cdewolf, pkremens, rsvoboda
Target Milestone: ER4   
Target Release: EAP 6.1.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-16 20:30:41 UTC Type: Component Upgrade
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: 975557, 975559, 981544, 1067555    
Bug Blocks:    

Description Kyle Lape 2013-06-18 18:50:04 UTC

Comment 1 Rostislav Svoboda 2013-06-20 09:59:49 UTC
QA NACK - see reasoning in BZ 975557#c1

Comment 2 James Perkins 2013-07-01 18:12:15 UTC
LogManager pull request https://github.com/jboss-logging/jboss-logmanager/pull/30. These fixes need to be merged into the logmanagers 1.4 branch, then a release needs to be cut. Once that is I can submit a PR with a 1.4.2.Final release of the logmanager.

Comment 3 Rostislav Svoboda 2013-07-02 06:26:58 UTC
Fixes in https://github.com/jboss-logging/jboss-logmanager/pull/30 are OK for QE, changing qa_ack

Comment 5 Petr Kremensky 2013-07-31 06:51:25 UTC
Verified on EAP 6.1.1 ER4