Bug 724783 (BRMS-621) - seam jar versions conflict
Summary: seam jar versions conflict
Keywords:
Status: VERIFIED
Alias: BRMS-621
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Build Process
Version: BRMS 5.2.0-Dev1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: BRMS 5.2.0.GA
Assignee: Julian Coleman
QA Contact:
URL: http://jira.jboss.org/jira/browse/BRM...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-08 14:42 UTC by Julian Coleman
Modified: 2023-05-01 08:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-16 21:13:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker BRMS-621 0 Blocker Closed seam jar versions conflict 2016-06-08 19:01:04 UTC

Internal Links: 728917

Description Julian Coleman 2011-07-08 14:42:11 UTC 
securitylevel_name: Public

BRMS contains Seam 2.1.0.GA from Drools:

  brms-standalone-5.2.0.dev2/jboss-as-web/server/*/deploy/jboss-brms.war/WEB-INF/lib/jboss-seam-remoting-2.1.0.GA.jar
  brms-standalone-5.2.0.dev2/jboss-as-web/server/*/deploy/jboss-brms.war/WEB-INF/lib/jboss-seam-2.1.0.GA.jar

but EAP 5.1.1 will contain Seam 2.2.3.EAP5.

The version from Drools should be updated with the verison from EAP/EWP.
Comment 1 lcarlon 2011-08-15 04:05:12 UTC 
Release note not required as per https://issues.jboss.org/browse/BRMS-621
Comment 2 Tihomir Surdilovic 2011-08-16 21:13:02 UTC 
I do not see the need to do this (see also comments on related bug 728917). Guvnor/BRM has maintained its independent Seam version in the war since BRMS 5.0. Since it is a war deployment it is isolated on the CL level by default in EAP. Even though Seam2 (supported version) does ship with EAP, customers do not have to use it in their applications, and it is not automatically deployed on server startup. Given that Guvnor is moving to Seam3 in the future, I really do not see a reason to do such a change now.
Comment 3 Ryan Zhang 2011-08-31 08:02:54 UTC 
This issue should be resolved since Bug 728917 has been fixed.
So I reopen  it and put state on ON_QA for verification
Comment 4 Ryan Zhang 2011-08-31 08:04:07 UTC 
This should be resolved on 5.2 ER3.
Comment 5 Lukáš Petrovický 2011-08-31 12:34:53 UTC 
BRMS 5.2 no longer fails to deploy on any container. VERIFIED.
Note You need to log in before you can comment on or make changes to this bug.