Bug 975555 - Upgrade JBoss LogManager for EAP 6.1.1
Summary: Upgrade JBoss LogManager for EAP 6.1.1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER4
: EAP 6.1.1
Assignee: James Perkins
QA Contact:
URL:
Whiteboard:
Depends On: 975557 975559 981544 1067555
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-18 18:50 UTC by Kyle Lape
Modified: 2014-02-20 16:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-16 20:30:41 UTC
Type: Component Upgrade
Embargoed:

Attachments (Terms of Use)

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
Note You need to log in before you can comment on or make changes to this bug.