+1 for this approach. On Apr 3, 2012, at 12:20 AM, Gunnar Morling wrote:
> Hi, > > thanks for your feedback. > > I think we might go for a combined approach. For everything not > related to method validation (that is, the api/spi split related > changes), I've now added deprecation markers and at the same time the > new types [1]. So clients could adapt to these changes based on 4.3 > and we can remove the old stuff in HV 5. That is, we're using the > deprecation mechanism as intended. > > This generally works pretty good, although it causes some name > changes, if for instance the return type of a method changes (there > can't be two methods with the same name but different return type). > > For the method validation API I've added deprecation markers, so that > users are informed about the upcoming change. In HV 5 we still can > decide whether to keep the old API around or remove it instantly. As > you say, this should be documented in the Wiki or release notes as > well. _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
