Yeah, the problem was that to *implement* BasicLogger we had switched to using a base class (bundled in 3.1) to implement the multitude of methods, due to problems associated with generating all the implementations in every class.
On 11/09/2011 08:39 AM, Steve Ebersole wrote: > Ok, I am totally confused then. I thought this was a discussion about > BasicLogger. But we have been using that afaik way before our recent > upgrade to 3.1 > > On Wed 09 Nov 2011 08:23:33 AM CST, David M. Lloyd wrote: >> On 11/09/2011 08:22 AM, Hardy Ferentschik wrote: >>> On Wed, 09 Nov 2011 15:00:07 +0100, Steve Ebersole <st...@hibernate.org> >>> wrote: >>> >>>> Maybe instead of "shading in" the removed class you could just add it >>>> back to the JBoss Logging codebase? >>> >>> Right, why can we not do that? >> >> You have it backwards. We didn't *remove* a class, we *added* one - >> which makes it not present in 3.0.x. >> >>>> On 11/09/2011 04:48 AM, Emmanuel Bernard wrote: >>>>> I see a few outputs >>>>> >>>>> - JBoss Logging 3.1.0.Final is released in the next 24h and we use it >>>>> in Core and Search >>> >>> What's stopping a 3.1.0.Final release? >> >> Trying to resolve this issue for you guys. >> >> > -- - DML _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
