We shouldn't need deprecated stuff in realm model and user model. That's what the
migration stuff is there to do.
Problem with regards to json representations is that we don't have an elegant way to
deal with migration. If we add that we won't have the problem of keeping deprecated
stuff around and it'll just be a matter of keeping some json transformation classes
similar to what we do for jpa/mongo.
----- Original Message -----
From: "Bill Burke" <bburke(a)redhat.com>
To: keycloak-dev(a)lists.jboss.org
Sent: Friday, 17 July, 2015 2:29:48 AM
Subject: [keycloak-dev] deprecated removals in future
We're accumulating deprecated metadata in models and data model.
Eventually we should draw a line in the sand and say we will only
support migration from a certain version to current.
i.e. Keycloak 2.0 would only allow migration from the last 1.x version.
We need to clean all the old stuff out prior to product.
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev