Bug 794449 (JBEPP-1489)

Summary:	jgroups version used in EPP 5.2 is not synchronized with the version shipped by the corresponding EAP.
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Gary Hu <garyhu2>
Component:	Portal Packaging	Assignee:	Jean-frederic Clere <jclere>
Status:	VERIFIED ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	5.2.0.GA	CC:	epp-bugs, mvecera, theute
Target Milestone:	---
Target Release:	5.2.1.CR02
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1489
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:

Description Gary Hu 2012-01-24 20:53:44 UTC

project_key: JBEPP

The jgroups versions used in EPP 5.2 are jgroups-2.6.13.GA.jar and jgroups-2.11.1.Final.jar. Why we need these two jars?

The jgroups 2.6.13 is used in EAP 5.0 and it's missing a lot of bug fixes. 2.11.1.Final is a newer version than anything we support.

Why can't we use the same jgroups version 2.6.19 shipped by the corresponding EAP?

Comment 1 Thomas Heute 2012-01-24 20:59:50 UTC

I guess it's been accidentally pulled from Maven dependencies

Comment 2 Michal Vanco 2012-04-10 18:02:16 UTC

There is still a difference at jgroups*jar versions.
EAP version is 2.6.20 - this versions is present at all/lib or production/lib as jgroups.jar.
But default configuration contains following:
server/default/deploy/gatein.ear/lib/jgroups-2.11.1.Final.jar

Assigning back to dev, version should be unified with EAP.