Re: Recent change causing TCK regressions

2010-02-14 Thread Donald Woods
Everything is passing again w/o any changes. Looks like it was just a timing issue -Donald On 2/13/10 10:02 PM, Patrick Linskey wrote: > What's the failure? > > 1509 is much more likely than 1507, as it's a change to allow enums to > be assigned in bulk updates. It's within the realm of r

Re: Recent change causing TCK regressions

2010-02-13 Thread Patrick Linskey
What's the failure? 1509 is much more likely than 1507, as it's a change to allow enums to be assigned in bulk updates. It's within the realm of reason that JPQL forbids such assignments -- I didn't check, and just assumed that the lack of enum support was a holdover from the 1.4 days. IM

Recent change causing TCK regressions

2010-02-13 Thread Donald Woods
Some change in the last day is causing a 1.0b TCK regression on trunk. When I get a chance, I'll try backing out the changes for 1509 or 1507 and see which one caused it. -Donald