For details:
http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
Hi Andrea,
the email subject mentions 5.0.9, the blog talks about 5.2.1 .. did we
release both?
Thanks,
Sanne
On 1 July 2016 at 09:13, andrea boriero wrote:
> For details:
> http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
> ___
> hibe
sorry for the previous wrong subject,
Hibernate ORM 5.2.1.Final has been released
For details:
http://in.relation.to/2016/06/30/hibernate-orm-521-final-release/
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailma
i have just realized and sent a new message with the correct subject.
Thanks
On 1 July 2016 at 10:16, Sanne Grinovero wrote:
> Hi Andrea,
> the email subject mentions 5.0.9, the blog talks about 5.2.1 .. did we
> release both?
>
> Thanks,
> Sanne
>
> On 1 July 2016 at 09:13, andrea boriero wro
Congrats, Andrea for the release.
Vlad
On Fri, Jul 1, 2016 at 11:19 AM, andrea boriero
wrote:
> i have just realized and sent a new message with the correct subject.
>
> Thanks
>
> On 1 July 2016 at 10:16, Sanne Grinovero wrote:
>
> > Hi Andrea,
> > the email subject mentions 5.0.9, the blog t
As it is an addition of a method to an SPI interface, then no it will not
be breaking applications.
It may or may not affect integrations. The only implementations of
EnhancementContext
I know of are our implementations. So, certainly you could say that it
potentially breaks integrations. But
I think that is just an oversight back to the original impl of the JPA
metamodel. I cannot speak for the tests. I can definitely see the
argument for PluralAttribute#isAssociation logically returning false for @
ElementCollection.
The spec is very unclear about it unfortunately. WRT entities ac
People on Reddit complain that they cannot see the list of resolved issues
without being logged into JIRA:
https://www.reddit.com/r/java/comments/4qqo8p/hibernate_orm_521_has_been_released/
.
Can we make that change log visible without the need for an account?
Otherwise it's very hard for people t
That is an ongoing argument with Atlassian. So yes, there is a way. It
means disabling the GitHub integration. I personally find the solution
worse than the problem. Also realize that it is always available via the
SCM'ed changelog file:
https://github.com/hibernate/hibernate-orm/blob/master/ch
Maybe we could create an easier to remember link to the changelog on
github, something like
http://orm.hibernate.org/changelog/5.2.1.Final
On Fri, Jul 1, 2016 at 9:46 PM, Steve Ebersole wrote:
> That is an ongoing argument with Atlassian. So yes, there is a way. It
> means disabling the GitHub
We have several options, these alternatives work already:
-
https://hibernate.atlassian.net/issues/?jql=project%20%3D%20HHH%20AND%20fixVersion%20%3D%205.2.1
- https://raw.githubusercontent.com/hibernate/hibernate-orm/5.2.1/changelog.txt
the second option is similar to Steve's proposal but point
11 matches
Mail list logo
