Done.
Should be propagated momentarily.
On 8 janv. 2010, at 17:42, Tomasz Blachowicz wrote:
> Hi guys,
>
> In my sample code that is using JPA2 and Hibernate 3.5 I'm getting the error
> known as HHH-4581. JIRA says that it is fixed in trunk and scheduled for
> Beta3 release, but I'd like to give
Hi guys,
In my sample code that is using JPA2 and Hibernate 3.5 I'm getting the error
known as HHH-4581. JIRA says that it is fixed in trunk and scheduled for
Beta3 release, but I'd like to give it a try sooner. Unfortunately there are
no snapshots published in repo, so I can't grab the latest one
Testing it within AS is not my primary reason for agreeing to this beta.
As I said we clearly have a big enough body of work (113 issues) to go
ahead with the next beta.
>From my dev perspective the JPA criteria stuff is getting *very* close
to done (even the tck numbers there are looking great)
The cutoff for getting external libs integrated into the AS trunk for M2
is Jan 31. I'd consider holding it open a bit longer for Hibernate (at
most a week) if it meant getting feature complete and stable JPA2 impl.
I wouldn't want to hold it open though to go from 75% complete to 85% or
some s
We certainly have enough fixes (currently 113 [1]) in to warrant another
release to give people a chance to test these fixes out.
As far as inclusion in an AS release, well that depends on when the
"component cutoff" date is for this M2. Do you know for certain?
[1]
http://opensource.atlassian.c
Steve,
Is this expected to be the final build for AS M2? My vote is to build
3.5.0-Beta-3 soon and another (more JPA-2 feature complete) build in
February (for inclusion in AS M2). I don't care what we label the
February build (3.5.0-Beta-4 or 3.5 final).
An alternative would be to hold off on
