Bug 814323

Summary:	jBPM console war contains two different versions of log4j.
Product:	[JBoss] JBoss Enterprise BRMS Platform 5	Reporter:	Petr Široký <psiroky>
Component:	Build Process	Assignee:	Julian Coleman <jcoleman>
Status:	VERIFIED ---	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	BRMS 5.3.0.GA	CC:	rzhang
Target Milestone:	ER7
Target Release:	BRMS 5.3.0.GA
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Petr Široký 2012-04-19 15:17:24 UTC

Description of problem:
jBPM console war contains two different versions (1.2.9 and 1.2.14) of log4j, located in jbpm-console.war/WEB-INF/lib. Only one version should be there.

Version-Release number of selected component (if applicable):
BRMS 5.3.0 ER5

Comment 1 Ryan Zhang 2012-04-23 07:38:15 UTC

Update status to ON_QA. Please verify them against ER6.

Comment 2 Ryan Zhang 2012-04-23 07:52:52 UTC

Confirmed that not picked in ER6. Change status back.

Comment 4 Ryan Zhang 2012-05-11 11:24:27 UTC

This fix has been committed to project branch which BRMS 5.3 used.

This is obviously an improvement and contains no risk. It should be apply for blocker flag.

But it seems I can't set the blocker to ?. Is there any permission setting there for allow me to do this?

Comment 6 Petr Široký 2012-05-14 13:36:14 UTC

Verified fixed in 5.3.0 ER7. Only log4j-1.2.9. jar is present.

Comment 7 PnT Account Manager 2017-12-07 23:33:48 UTC

Employee 'msalatin' has left the company.