Bug 982541

Summary:	log4j - New version available: 2.0 beta7
Product:	[Fedora] Fedora	Reporter:	Marek Goldmann <mgoldman>
Component:	log4j	Assignee:	Mikolaj Izdebski <mizdebsk>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	devrim, mizdebsk, msrb, sochotni, tradej
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.0-0.1.rc1	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-16 05:47:11 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:	1091032, 1091034
Bug Blocks:

Description Marek Goldmann 2013-07-09 09:15:48 UTC

Description of problem:

The log4j project is going to release 2.0 soon:

http://logging.apache.org/log4j/2.x/

The latest version currently is 2.0 beta7.

It would be nice to upgrade to the latest pre-release. Additionally the JGroups project already uses it so it's blocking me currently.

The 2.0 ships with a 1.2 compatibility package (module log4j12-api).

Comment 1 Marek Goldmann 2013-07-09 09:26:01 UTC

It seems that JGroups can work with old Log4j 1.2, I'll use that code. So this bug is not blocking jgroups package upgrade anymore.

Comment 2 Fedora Admin XMLRPC Client 2014-04-24 12:46:54 UTC

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Mikolaj Izdebski 2014-05-16 05:46:59 UTC

Fixed in log4j-2.0-0.1.rc1

Comment 4 Mikolaj Izdebski 2014-05-16 05:47:11 UTC

I believe that this feature is included in log4j-2.0-0.1.rc1,
which is available in Fedora Rawhide, so I am closing this bug now.

The build which includes the feature can be found at Koji:
http://koji.fedoraproject.org/koji/buildinfo?buildID=516970