Hello all,
we're now ready for Hibernate ORM 5, last chance to make sure it's all right!
Details on the blog: http://in.relation.to/2015/07/13/hibernate-search-54CR1/
Thanks,
Sanne
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lis
Or should WildFly perhaps use
hibernate.implicit_naming_strategy=org.hibernate.boot.model.naming.ImplicitNamingStrategyJpaCompliantImpl
as the default?
Scott
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/
No, that is not the correct way. That would force all test classes to be
instrumented where we only need a few to be instrumented.
There are 2 options:
1) Move all the tests that require instrumentation into a new SourceSet and
then associate the instrument task with that SourceSet only.
2) Use
No. And possibly.
This is one of those things similar to "use new id generator mappings".
For new development I think it probably makes sense for WildFly users to
expect JPA-compliant implicit naming.The difficulty is how changing
that would affect existing applications.
On Mon, Jul 13, 2015
OK, got it.
Thanks!
Gail
- Original Message -
> From: "Steve Ebersole"
> To: "Gail Badner" , "Hibernate"
>
> Sent: Monday, July 13, 2015 3:43:21 PM
> Subject: Re: [hibernate-dev] How should hibernate-entitymanager test classes
> be instrumented?
>
> No, that is not the correct way. T
Now that 5.0 development is settling down, I think its time to go ahead and
start on this. Should we start next week? We never discussed a day. I am
thinking Monday or Tuesday. Does that work for everyone interested?
Ultimately the idea is for this meeting to address incoming HHH issues.
But I
