Here is the list of proposed topical guides i started:
https://github.com/hibernate/hibernate-orm/wiki/ProposalTopical-Docs
On Thu 10 Oct 2013 11:47:03 AM CDT, Steve Ebersole wrote:
> We actually made use of the topics feature of the bot today :) One
> got missed by the bot...
>
>
> [11:38
We actually made use of the topics feature of the bot today :) One got
missed by the bot...
[11:38] Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2013/hibernate-dev.2013-10-10-14.55.html
[11:38] Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenod
It is a valid point, it might raise the bar but I would be very
surprised if the rise would be significant.
It's indeed a tradeoff vs. benefits, and as Emmanuel pointed out, the
benefits are not significant either, at least in our usage of the new
style coding.
I proposed to make the switch (was
On 9 Jan 2013, at 4:20 PM, Steve Ebersole wrote:
> OGM itself is new, but at the end of the day its a JPA provider which is
> not new. Basing on Java 7 will limit adaption from folks wanting to
> drop OGM in to their app as replacement for their JPA provider to give
> it a spin in certain en
2013/10/9 Steve Ebersole
> What is gained needs to be balanced by what you are giving up.
>
> OGM itself is new, but at the end of the day its a JPA provider which is
> not new. Basing on Java 7 will limit adaption from folks wanting to drop
> OGM in to their app as replacement for their JPA pro
2013/10/9 Emmanuel Bernard
> No strong opinion.
> To me Java 7 is of little value. Java 8 on the other hand...
>
:)
>
> BTW, will we have trouble with servers that do expect Java 6? I suspect
> WF is already on 7 so we don't have that problem on that side.
>
Yes, WF as EE 7 container must "pr
