Won't this break like every existing example and 3rd party integrations
(think Spring projects) maven and gradle builds on the planet
? Or are hibernate 6 so radically different there is no chance you would
just change the version number to have
builds work with both hibernate 5 and 6 ?
Not saying it should not be done - just wondering if we grok the full
impact for users.
/max
> No concerns.
> When talking about this with Steve I also added it to our next meeting
> agenda, however it looks like we're all onboard so maybe there isn't
> much to debate :)
>
> On 4 October 2016 at 19:19, Gunnar Morling <gun...@hibernate.org>
> wrote:
>> Hi,
>>
>> I just stumbled across HHH-11153 ("Rename published groupId from
>> org.hibernate to org.hibernate.orm"), scheduled for ORM 6.0.0.Alpha1.
>>
>> I think that's a great idea and would suggest we do the same for
>> Hibernate
>> Validator and Search in their respective 6.0 releases:
>> org.hibernate.validator and org.hibernate.search (for OGM we used
>> org.hibernate.ogm from the beginning).
>>
>> Any concerns?
>>
>> --Gunnar
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
/max
http://about.me/maxandersen
_______________________________________________
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
