Closed sonOfRa closed 1 year ago
Thanks for providing this. But I'm currently no sure if I really want to provide a new version of the legacy branch. As I wrote, the legacy branch was out of maintenance as soon the Quarkus distribution was released.
Keeping a fork internally until we've migrated to quarkus works for us. If you change your mind, and you want to merge and release this anyways, feel free to reopen it. Thank you for the quick responses!
I left this as a draft for now, not sure if you still want to support changes to the v1 branch. I'm currently in the process of updating a large installation to 19-legacy, and going to 19-quarkus from there, so it would be useful to have a version with support for Keycloak 19-legacy around. If you don't need this, I'll maintain it in a private registry for the time that we need for the migration to quarkus.