Bug 1309248

Summary: To align the keycloak version between projects in Integration Platform products
Product: [Retired] JBoss BPMS Platform 6 Reporter: Ryan Zhang <rzhang>
Component: Build and AssemblyAssignee: Ryan Zhang <rzhang>
Status: CLOSED EOL QA Contact: Lukáš Petrovický <lpetrovi>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0   
Target Milestone: ER1   
Target Release: 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 19:10:03 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 2016-02-17 10:28:49 UTC
Description of problem:
For BxMS 6.3, we are depending on keycloak versions.
For example in DR1 release, errai depends on keycloak 1.7.0.Final.
uberfire-extension depends on keycloak 1.4.0.Final.

And for GA release, it definitely needs to be upgrade.

So the request here is to add keycloak into jb-ip-bom , so it will be easy to keep projects use the same version keycloak.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Ryan Zhang 2016-02-17 10:49:22 UTC
As far as I can tell, errai and uberfire-extension are depending on keycloak artifacts.
So we would also need to errai and uberfire-extension to remove the dependencyManagement for keycloak and use the one defined in jb-ip-bom after this has been added into the jb-ip-bom.

Comment 4 Ryan Zhang 2016-02-23 08:01:21 UTC
Since the PR has been merged to jb-ip-bom, this issue is fixed.
The jb-ip-bom should be ready for ER1 release(not for DR2).
And  no effort is  needed from QE since this can be verified in build stage.