Bug 1309248 - To align the keycloak version between projects in Integration Platform products
To align the keycloak version between projects in Integration Platform products
Status: VERIFIED
Product: JBoss BPMS Platform 6
Classification: JBoss
Component: Build and Assembly (Show other bugs)
6.3.0
Unspecified Unspecified
high Severity high
: ER1
: 6.3.0
Assigned To: Ryan Zhang
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-17 05:28 EST by Ryan Zhang
Modified: 2016-02-23 03:01 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Zhang 2016-02-17 05:28:49 EST
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 05:49:22 EST
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 03:01:21 EST
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.

Note You need to log in before you can comment on or make changes to this bug.