Move keycloak client libs into separate repository #30787
Labels
area/adapter/saml
area/admin/client-java
area/authorization-services
Indicates an issue on Authorization area
area/dependencies
area/oidc
Indicates an issue on OIDC area
kind/epic
team/core-clients
Description
Following Keycloak artifacts needs a separate repository and no dependency on Quarkus:
The dedicated repository already created https://github.com/keycloak/keycloak-client
We need to be able to release these artifacts independently of the Keycloak server release.
Ideally, the artifacts should not have any dependency on artifacts from
keycloak
repository (with the exception of the testsuite inkeycloak-client
repository, which probably can have a dependency onkeycloak
repository to be able to consume and run Keycloak server) and similarlykeycloak
repository should not have any dependency on those.Because
keycloak
repository still need to use some of those artifacts in it's testsuite (likekeycloak-admin-client
and probably alsokeycloak-authz-client
), it is possible that we may need to keep Java classes in thekeycloak
repository and have some mechanism for copying/syncing Java classes fromkeycloak
repository to thekeycloak-client
repository.Some of the modules can be possibly directly moved to the separate repository as they are not used in much Keycloak tests, so the corresponding tests can be moved as well to client repository (maybe policy-enforcer, but this is to be investigated).
Optional targets
Handle also those artifacts to separate repository:
But those are not needed by Quarkus and hence don't have so much priority
Motivation
Cyclic dependency on Quarkus needs to be broken.
Tasks
keycloak/keycloak
keycloak-client#34The text was updated successfully, but these errors were encountered: