On 08/02/2012 12:56 AM, Gail Badner wrote:
> These tests fail with org.hibernate.cfg.NotYetImplementedException when the
> sources are being processed. For some reason. this failure is not recognized
> as an expected failure. I'm not sure of the reason for this.
I was looking at this a little be
On 08/02/2012 07:39 PM, Gail Badner wrote:
>
> IIRC, there were some tests that were annotated with @FailureExpected that
> were only expected to fail using some dialects. This was causing what looked
> like failures on the dialects where the test was expected to pass. When we
> were trying to
I have not heard anything so I will coordinate with the SourceForge
team this week about pulling the trigger on this.
On Wed 18 Jul 2012 10:29:58 AM CDT, Steve Ebersole wrote:
> Not sure if y'all are tracking what is going on at SourceForge. They
> have done a redesign of the site using a new h
- Original Message -
> From: "Steve Ebersole"
> To: "Gail Badner"
> Cc: "Hibernate hibernate-dev"
> Sent: Monday, August 6, 2012 6:24:42 AM
> Subject: Re: [hibernate-dev] Unit test failures using the new metamodel
>
>
> On 08/02/2012 12:56 AM, Gail Badner wrote:
> > These tests fail
- Original Message -
> From: "Steve Ebersole"
> To: "Gail Badner"
> Cc: "Hardy Ferentschik" , "Hibernate hibernate-dev"
>
> Sent: Monday, August 6, 2012 7:02:54 AM
> Subject: Re: [hibernate-dev] Unit test failures using the new metamodel
>
>
> On 08/02/2012 07:39 PM, Gail Badner wro
I've seen some cases where tests are passing for functionality that is not yet
implemented. In these cases, generated DDL for the new metamodel is incorrect.
For example:
org.hibernate.test.annotations.genericsinheritance.GenericsInheritanceTest
Generated DDL using old metamodel:
create table
