Bug 794449 (JBEPP-1489) - jgroups version used in EPP 5.2 is not synchronized with the version shipped by the corresponding EAP.
Summary: jgroups version used in EPP 5.2 is not synchronized with the version shipped ...
Keywords:
Status: VERIFIED
Alias: JBEPP-1489
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal Packaging
Version: 5.2.0.GA
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.1.CR02
Assignee: Jean-frederic Clere
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-24 20:53 UTC by Gary Hu
Modified: 2018-02-06 19:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1489 0 Major Closed jgroups version used in EPP 5.2 is not synchronized with the version shipped by the corresponding EAP. 2013-11-13 07:39:03 UTC

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