Recovery would be a bit of work as I also removed methods from
KeycloakSession, the UserFederationManager, and ported relevant tests.
Do a 2.5 release. We've been telling people for a long time that this
SPI would be removed. Then again, its been undocumented for a long time
On 11/24/16 5:10 AM, Stian Thorgersen wrote:
Just saw the other threads that it's already removed. We could
recover them and mark them deprecated or remove and do a 2.5 release.
Whatever you think is best.
On 24 November 2016 at 11:07, Stian Thorgersen <sthorger(a)redhat.com
Actually thinking about this some more. Why don't we just keep the
old user federation SPI in for now and mark them as deprecated.
Then we can remove in 3.0.0C.CR1 release instead? Makes more sense
to remove in a major update rather than a minor update. That would
also give you more time on figuring out the migration issue?
On 23 November 2016 at 21:22, Bill Burke <bburke(a)redhat.com
Next community release should be 2.5 not 2.4.1. Since we are
support for the User Federation SPI, this will break backward
campatibility with 2.4.0.Final. Point releases should not break
backward compatibility so, IMO, the next community release
2.5.0, not 2.4.1.
keycloak-dev mailing list