We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I was looking at quickstarts for RHBK, I figured some small issues in our keycloak-quickstarts:
Quickstarts still have dependency on Wildfly 28 Beta. Can be good to update them to newer 28.0.1.Final
Some extension quickstarts still mention Java 11, but they require Java 17. That is the only version, which Keycloak 22+ supports.
When running tests with latest Chrome, it can be also worth to mention to use latest Chrome driver. Added some notes about it
There are some other minor inaccuracies in README files (incorrect ports or URLs in some quickstarts etc, incorrect maven profiles etc)
No response
The text was updated successfully, but these errors were encountered:
Quickstarts - Wildfly upgrade and README cleanup
c2f68a1
closes keycloak#505 Signed-off-by: mposolda <mposolda@gmail.com>
28bbb08
757ffaf
7578786
closes #505 Signed-off-by: mposolda <mposolda@gmail.com>
mposolda
Successfully merging a pull request may close this issue.
Description
When I was looking at quickstarts for RHBK, I figured some small issues in our keycloak-quickstarts:
Quickstarts still have dependency on Wildfly 28 Beta. Can be good to update them to newer 28.0.1.Final
Some extension quickstarts still mention Java 11, but they require Java 17. That is the only version, which Keycloak 22+ supports.
When running tests with latest Chrome, it can be also worth to mention to use latest Chrome driver. Added some notes about it
There are some other minor inaccuracies in README files (incorrect ports or URLs in some quickstarts etc, incorrect maven profiles etc)
Discussion
No response
Motivation
No response
Details
No response
The text was updated successfully, but these errors were encountered: