Hi Steve. Can you shed some light on the deprecation warnings that started to appear in 3.5.2 in org.hibernate.Hibernate? I see they're related to type system changes your making for 3.6 under HHH-5138 and HHH-5182, but it's not clear what part of those landed in 3.5.x or what migration steps developers need to take to get rid of the warnings. Nothing jumps out at me in the changelog. Thanks. _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

On Thu, Jul 8, 2010 at 11:09 AM, Steve Ebersole <steve(a)hibernate.org&gt; wrote: Sure. What are you looking for exactly? The new calls? They do not exist until 3.6 Hmm, if the new calls aren't there, then why are the old ones deprecated in 3.5? Our build process complains when we make calls into deprecated code, so I'd like to eliminate those if I can.

On Thu, Jul 8, 2010 at 11:28 AM, Steve Ebersole <steve(a)hibernate.org&gt; wrote: Because thats how I use deprecation. See http://opensource.atlassian.com/projects/hibernate/browse/HHH-5212 for a discussion about this. OK, after reading HHH-5212, I understand you're argument, although I agree with Anders' points. As an app developer, this puts me in the unfortunate position of having to tell my team to ignore these build warnings or find a way to suppress them selectively, since there's no other action I can take to "fix the problem" if I use 3.5.