Bug 1038023

Summary:	Make uberfire and jbpmmigration use community bom
Product:	[Retired] JBoss BRMS Platform 6	Reporter:	Ryan Zhang <rzhang>
Component:	Build and Assembly	Assignee:	Alexandre Porcelli <porcelli>
Status:	CLOSED WONTFIX	QA Contact:	Lukáš Petrovický <lpetrovi>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.0.0	CC:	etirelli, pzapataf
Target Milestone:	CR1
Target Release:	6.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-04 14:11:21 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:

Description Ryan Zhang 2013-12-04 09:42:43 UTC

Description of problem:
Most of projects in jboss integration have used community bom to align the thirdparty dependencies. 

Should we also make uberfire and jbpmmigration do the same?

And what about mvel?

Using community bom for these project can make the dependencies in product more consistent.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Edson Tirelli 2013-12-04 13:37:25 UTC

Porcelli, can you please check this for Uberfire. 

The migration tool is not part of any released product AFAIK. It is an independent tool, so I am not sure this is a requirement. I will ask Pedro to check.

Comment 3 Pedro Zapata 2013-12-04 14:02:22 UTC

The migration tool is built independently and it's not even dependant on a product release (it's a project release). This should not be a requirement for the migration tool, since we agreed to built from community sources to avoid costly rewrites.

Comment 4 Edson Tirelli 2013-12-04 14:11:21 UTC

I discussed this with Porcelli and Mark Proctor. 

Uberfire is splitting up and moving to a new group that is not part of the jboss-integration projects. One of the requirements was that we make it completely independent of anything BRMS/BPMS related because it will be used by other groups on their own platforms (like EAP, etc).

In our understanding, we can't have uberfire depending on a jboss-integration pom/bom. 

I am closing this ticket for now. We can discuss it during the PM meeting. Re-open if we find we need to do something else.

Comment 5 Ryan Zhang 2013-12-13 02:22:02 UTC

OK.

I raised another issue to fix the problem block the productization of uberfire. See https://bugzilla.redhat.com/show_bug.cgi?id=1042660

(though I think it would be easier to inherit the community bom parent rather than duplicate mantaining the same versions, I agreed your point makes to me.)