[hibernate-dev] 6.0 planning

[Emmanuel Bernard]

Yes I think that's reasonable.
My gut feeling is that there are only a handful HibernateException
subclass really useful when coding an application, breaking the rest is
probably fine.

On Mon 2016-04-04 15:55, Steve Ebersole wrote:
> So to me the biggest design question is in regard to exceptions.  Where
> possible I plan on integrating the 2 hierarchies (which probably means the
> Hibernate exceptions becoming interfaces).  In cases where such an
> integration is not possible we will have to err on the side of preferring
> the JPA exceptions.
> 
> Everyone ok with that?
> 
> 
> On Mon, Apr 4, 2016 at 10:37 AM Sanne Grinovero <sanne at hibernate.org> wrote:
> 
> > On 4 April 2016 at 15:48, Steve Ebersole <steve at hibernate.org> wrote:
> > > So there we go :)
> > >
> > > On Mon, Apr 4, 2016 at 9:37 AM Scott Marlow <smarlow at redhat.com> wrote:
> > >>
> > >> Hmm, just searched through irc history and came up with fixed by
> > >> https://hibernate.atlassian.net/browse/HHH-7552.  Nice to see this
> > >> already fixed!  ;)
> >
> > Great, so you could fix WildFly 10 to already benefit from it and
> > cleanup the classpath!
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev