Bug 1127232
Summary: | Uberfire dependency is misaligned to EAP 6.3 BOM | ||
---|---|---|---|
Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ryan Zhang <rzhang> |
Component: | Build and Assembly | Assignee: | Edson Tirelli <etirelli> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Lukáš Petrovický <lpetrovi> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.1.0 | CC: | etirelli, kverlaen, mwinkler, rrajasek, rzhang |
Target Milestone: | ER1 | ||
Target Release: | 6.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-16 19:37:42 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: | |
Embargoed: |
Description
Ryan Zhang
2014-08-06 12:42:08 UTC
Hi, Jonathan I have seen that Errai inherit the integration platform. If uberfire align with Errai BOM, it should transitively align to integraiton-bom. Just a few things I noticed: 1) Errai 3.1.0-SNAPSHOT currently use 6.0.0.CR9 community bom, however droolsjbpm use 6.0.0.CR11. So bpms/brms 6.1.0 require uberfire to align to 6.0.0.CR11 or new version in future. 2) Currently uberfire depends on errai 2.4.4.Final, when would uberfire depend on 3.1.x series? 3) It seems that Errai 3.1.0-SNAPSHOT needs to tidy up the dependency in the errai-bom . There are some dependency misalignment to integration-bom. But this probably needs a Bugzilla to raise against on Errai. (In reply to Jonathan Fuerth from comment #3) > Hi Edson, > > This is already one of the things on my to-do list. Specifically, we're > planning to align with the Errai BOM, because UberFire is built on Errai and > it should ideally align with all Errai dependencies. But this should > transitively get what you're asking for, since the Errai BOM inherits from > the platform integration BOM: > > https://github.com/errai/errai/blob/master/errai-bom/pom.xml > > PS: do these comments really need to be marked private? Hi Ryan, Thanks for the analysis! To answer question 2: BxMS 6 currently depends on UberFire 0.4.[latest]. However, work is underway in the community projects to update to UberFire 0.5.[latest]. UberFire 0.4 depends on Errai 2.4.[latest], and the Errai 2.4 BOM depends on jboss-parent, not platform-integration-parent. Errai 2.4 is a maintenance branch at this point, only getting high priority patches. I expect a major BOM update to this version of Errai wouldn't be appropriate at this point. UberFire 0.5 depends on Errai 3.0.[latest], and this BOM also depends on jboss-parent. UberFire 0.6 will depend on Errai 3.1, but UberFire 0.6 doesn't exist yet, so it's much too early to say when we could expect BxMS to switch to UF 0.6. Given the above, I'm thinking it would be best to connect the UberFire 0.4 and 0.5 BOMs directly to the platform integration BOM, and wait for UF 0.6 + Errai 3.1 to connect the UF BOM to the Errai BOM. What do you think? As for points 1 and 2, these issues should be easy to solve with a couple of pull requests to Errai 3.1. (In reply to Jonathan Fuerth from comment #5) > Hi Ryan, > > Thanks for the analysis! > > To answer question 2: > > BxMS 6 currently depends on UberFire 0.4.[latest]. However, work is underway > in the community projects to update to UberFire 0.5.[latest]. > > UberFire 0.4 depends on Errai 2.4.[latest], and the Errai 2.4 BOM depends on > jboss-parent, not platform-integration-parent. Errai 2.4 is a maintenance > branch at this point, only getting high priority patches. I expect a major > BOM update to this version of Errai wouldn't be appropriate at this point. > > UberFire 0.5 depends on Errai 3.0.[latest], and this BOM also depends on > jboss-parent. > > UberFire 0.6 will depend on Errai 3.1, but UberFire 0.6 doesn't exist yet, > so it's much too early to say when we could expect BxMS to switch to UF 0.6. > > Given the above, I'm thinking it would be best to connect the UberFire 0.4 > and 0.5 BOMs directly to the platform integration BOM, and wait for UF 0.6 + > Errai 3.1 to connect the UF BOM to the Errai BOM. What do you think? That sounds very good to me. > > As for points 1 and 2, these issues should be easy to solve with a couple of > pull requests to Errai 3.1. Yes, Agreed! Thanks! I will put the unmatch list here if any mistach happens after I upgrade the alginment EAP 6.4.2. Set the target release on ER1 |