No word on the new test case I take it?
WRT the HHH72 logged warnings, like i said the warning is inocuous.
But I did correct it: https://hibernate.atlassian.net/browse/HHH-9797
On Wed, May 13, 2015 at 3:52 PM, Steve Ebersole wrote:
> Nope. Well, specifically yes your test fails as is. Bu
Hi Steve,
your test indeed works fine - I logged here
https://jira.spring.io/browse/SPR-11694 so that the spring guys will have a
look, but I don't think spring is doing any magic on the foreign keys.
Juergen Hoeller from spring proposed it might be a bug in Hibernate's
EntityManager implementatio
Hi Guillaume, welcome back!
I love the usability of this, I agree we should expose this
functionality. The "text()" method seems a good choice too.
On some other details:
- ignoreAnalyzer() I agree with your comment, it doesn't seem to make
much sense. But what about not having the method rathe
Please do not push any commits until after 4.3.10.Final is released.
Thanks,
Gail
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
So you're original test was using JPA? See this illustrates why it's best
to isolate tests down to SSCCE.
I will try again with JPA specifically.
On May 14, 2015 11:30 AM, "Petar Tahchiev" wrote:
> Hi Steve,
>
> your test indeed works fine - I logged here
> https://jira.spring.io/browse/SPR-116
It's all working now but I copied a couple of utility classes from
ORM, as they were part of the tests.
essentially I needed JdbcConnectionAccessImpl :
-
https://github.com/hibernate/hibernate-search/commit/12df1b654cefad17b5186e3d3f4c5419d41295d1#diff-f3753a568f2086a66b118016751498edR21
Filed H
You mean the testing impl/variants of these?
On May 14, 2015 6:55 PM, "Sanne Grinovero" wrote:
> It's all working now but I copied a couple of utility classes from
> ORM, as they were part of the tests.
> essentially I needed JdbcConnectionAccessImpl :
> -
> https://github.com/hibernate/hibernat
Actually that cannot be it. JPA does not define schema update capability.
On May 14, 2015 4:27 PM, "Steve Ebersole" wrote:
> So you're original test was using JPA? See this illustrates why it's best
> to isolate tests down to SSCCE.
>
> I will try again with JPA specifically.
> On May 14, 2015
For details, see: http://in.relation.to/Bloggers/HibernateORM4310FinalReleased
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Following Steve's suggestion using resolutionStrategy, I was able to build the
hibernate-infinispan jar with Infinispan 6.0.0.Final and run the unit tests
with 7.2.1.Final.
I'm sure there's a more elegant way to do this, so I've created a new jira
(HHH-9802) and a pull request with the change I
10 matches
Mail list logo
