Currently we are still working on 6.0 "on top" of 5.2, meaning that all of
the changes we are proposing to ORM for 6.0 are kept in a separate
repo/project using ORM 5.2 as a dependency.
As I work on 6.0 I have come across a change that I would like to make that
requires that I change something in
Hi everyone!
Here are the transcripts of this week's NoORM IRC meeting:
15:54 < jbott> Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2016/hibernate-dev.2016-06-07-13.04.html
15:54 < jbott> Minutes (text):
Too bad we can't just publish a Docker image.
Is this something we'd publish somewhere (Nexus/Artifactory)? I know
nothing about building a WF module ZIP. But if you are willing to do the
work and it helps OGM etc, of course we would incorporate it.
On Tue, Jun 7, 2016 at 8:19 AM Gunnar
Hello,
actually I would like to learn how the FetchMode.JOIN is supposed to
work in case of cycles (not really cycles but MetamodelGraphWalker
considers them cycles).
Check the test case please - it gets LazyInitializationException on a
relation despite that relation being marked as JOIN
Hello,
What about backporting the JCache module?
Since JCache is Java 1.6, that could make it available to more users.
I believe there have been small API changes between 5.1 and 5.2 but still
the porting should be easy enough and I am willing to help for that.
Regards,
Louis
On Tue, Jun 7,
I agree that the wording should be changed. That sentiment is true of
many, many exceptions.
On Tue, Jun 7, 2016 at 8:21 AM Emmanuel Bernard
wrote:
> We probably should change this message.
> When was the last time this message was due to a bug in our logic?
> I can't
We probably should change this message.
When was the last time this message was due to a bug in our logic?
I can't remember a time when this was the case personally.
Thoughts?
On Sun 2016-06-05 17:17, Petar Tahchiev wrote:
> Hello,
>
> I'm using hibernate version 5.1.0.Final and
So long as we limit that to the Stream access, +1
On Tue, Jun 7, 2016 at 5:07 AM andrea boriero wrote:
> it sounds reasonable to me
>
> On 7 June 2016 at 10:57, Vlad Mihalcea wrote:
>
> > To get a picture of why we need this, consider the
Hi,
As discussed by some of us during the No ORM meeting in May, it'd be great
if there was a module ZIP allowing people to easily upgrade Hibernate ORM
in the WildFly version they are using.
Just the other day there was a blog post published [1] describing how to
use Hibernate ORM 5.2 in WF 10,
I have mentioned this before. We cannot automate this through Gradle (long
story, feel free to see my Gradle Jiras and forum posts for details). And
I am not going to make this a manual step for each and every release.
On Tue, Jun 7, 2016 at 3:42 AM Sanne Grinovero wrote:
If you send a PR I will include it.
On Sun, Jun 5, 2016 at 11:00 AM Sanne Grinovero wrote:
> I just noticed that the org.hibernate.Query interface was deprecated
> in 5.2, with the suggestion to use org.hibernate.query.Query now.
> That's ok, but it seems the "deprecation
it sounds reasonable to me
On 7 June 2016 at 10:57, Vlad Mihalcea wrote:
> To get a picture of why we need this, consider the following example from
> the docs:
>
> Stream
HHH-10745, runnable test case attached to that issue
(org.hibernate.test.fetchprofiles.cycle.tar.gz).
Thank you
Vladimir
On 06/07/2016 06:00 AM, Gail Badner wrote:
> Please create a Jira issue and attach a runnable test case.
> Thanks,
> Gail
>
> On Thu, Jun 2, 2016 at 5:45 AM, Vladimir
I've seen quite some people struggling with the upgrade to Hibernate
ORM 5.2 as they think that hibernate-entitymanager was either
mistakenly not uploaded, or wasn't synched to Maven Central yet.
Could we restore the pom.xml for this artifact and have it redirect to
hibernate-orm ?
Doing so
Hi,
Because 5.1 is the last version supporting 1.6, I think it's worth to
integrate as many fixes as we can that are now only available on the 5.2
branch.
Therefore, I collected a list of issues so that you can tell me which ones
you'd like me to cherry pick on 5.1: