Bug 1088638
| Summary: | RHEL6 RPMs: Upgrade log4j-jboss-logmanager to 1.1.0.Final-redhat-2 | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Fernando Nasser <fnasser> |
| Component: | RPMs | Assignee: | Yong Yang <yyang> |
| Status: | CLOSED ERRATA | QA Contact: | Katerina Odabasi <kanovotn> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.3 | CC: | pgier |
| Target Milestone: | CR2 | Keywords: | Rebase |
| Target Release: | EAP 6.2.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Rebase: Bug Fixes and Enhancements | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-05-27 23:51:55 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Fernando Nasser
2014-04-16 22:19:56 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 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 Verified in CR3 build. 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 |