Nice ! Congratulations =)
Niko
2013/12/5 Emmanuel Bernard :
> http://hibernate.org has been completely revamped.
>
> The entire team has been working on it for a long time. I am personally
> very happy to see this puppy out.
>
> Our goals were:
>
> * to help newcomers understand what each Hiberna
Per subject, Hibernate ORM 4.3.0.CR2 has just been released.
http://in.relation.to/Bloggers/HibernateORM430CR2Release
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Feel free to push again. I am finished with the repo at this point.
Need to get daughter from school and will finish up release
(announcements) tonight.
On Thu 05 Dec 2013 01:17:59 PM CST, Steve Ebersole wrote:
> I am starting the 4.3 CR2 release, please hold off from pushes for a bit
I am starting the 4.3 CR2 release, please hold off from pushes for a bit
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
http://hibernate.org has been completely revamped.
The entire team has been working on it for a long time. I am personally
very happy to see this puppy out.
Our goals were:
* to help newcomers understand what each Hibernate project is about and why it
matters
* to help regular / advanced users
On Thu, Dec 5, 2013 at 5:31 PM, Guillaume Smet wrote:
> I'm working on a pull request to fix the problem in search as
> requested by Steve.
Done: https://github.com/hibernate/hibernate-search/pull/521
--
Guillaume
___
hibernate-dev mailing list
hibern
Well, you won't have us test 4.2.8 as we are using Hibernate Search in
all our applications and we can't use them together. It might not be a
showstopper but we usually provide useful feedback on the releases of
orm and search.
I think we should either release a fix for search or orm but it's just
EntityKey is SPI, not API, so typically I allow changes to happen in minor
releases (especially in this case where multiple changes were necessary for
Wildfly/EAP). That being said, not deprecating the existing constructor was an
stupid oversight on my part -- I pulled in a dozen commits at onc
Can't (read you should be!) you use
org.hibernate.engine.spi.SessionImplementor#generateEntityKey ?
Its signature hides the values from Session actually kept on the
genernated EntityKey:
public EntityKey generateEntityKey(Serializable id, EntityPersister
persister);
That signature has not ch
Yes. This commit looks really nice: that's what looks really
interesting to me in 4.2.8. But providing a compatibility layer seems
necessary.
On Thu, Dec 5, 2013 at 5:06 PM, Scott Marlow wrote:
> Looks like this commit changed that
> https://github.com/hibernate/hibernate-orm/commit/bf26311474257
Looks like this commit changed that
https://github.com/hibernate/hibernate-orm/commit/bf26311474257c2f0118615e003553095c2d87b0
On 12/05/2013 10:51 AM, Guillaume Smet wrote:
> Hi all,
>
> ORM 4.2.8.Final breaks the API of EntityKey as it removes tenantId
> from the constructor.
>
> Typically, in H
Hi all,
ORM 4.2.8.Final breaks the API of EntityKey as it removes tenantId
from the constructor.
Typically, in HSearch, we have the following call:
https://github.com/hibernate/hibernate-search/blob/master/orm/src/main/java/org/hibernate/search/query/hibernate/impl/PersistenceContextObjectsInitia
12 matches
Mail list logo
