Well 3.6 (trunk) is pretty much code complete at this point unless
something major comes up. At this point we are simply working on the
documentation since the changes in 3.6 require significant reworking of
the docs.
I point this out since you could in fact start using 3.6
On Thu, 2010-07-08 a
On Thu, Jul 8, 2010 at 11:28 AM, Steve Ebersole 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
Because thats how I use deprecation. See
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5212 for a
discussion about this.
On Thu, 2010-07-08 at 11:21 -0400, Rob Hasselbaum wrote:
> On Thu, Jul 8, 2010 at 11:09 AM, Steve Ebersole
> wrote:
> Sure. What are you looking for
On Thu, Jul 8, 2010 at 11:09 AM, Steve Ebersole 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 cod
Sure. What are you looking for exactly?
The new calls? They do not exist until 3.6
On Thu, 2010-07-08 at 09:51 -0400, Rob Hasselbaum wrote:
> 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 t
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 devel
