Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-14 Thread Sanne Grinovero
On 13 December 2017 at 13:34, Steve Ebersole wrote: > > > On Wed, Dec 13, 2017 at 7:05 AM Sanne Grinovero wrote: >> >> Not really. Think of it as Deprecation: it will trigger some warnings >> for end users, especially those who didn't get the "news" of

Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-14 Thread Sanne Grinovero
On 13 December 2017 at 13:23, Gunnar Morling wrote: > Just to be sure, including an EPL-licensed item is fine as far as WildFly is > concerned? Other than that, +1 for that change. To clarify on this, and better answer Yoann's concern which I didn't address properly before:

Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-13 Thread Steve Ebersole
On Wed, Dec 13, 2017 at 7:05 AM Sanne Grinovero wrote: > Not really. Think of it as Deprecation: it will trigger some warnings > for end users, especially those who didn't get the "news" of moving to > the new API, and keep things working for a little longer for those >

Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-13 Thread Gunnar Morling
Just to be sure, including an EPL-licensed item is fine as far as WildFly is concerned? Other than that, +1 for that change. 2017-12-13 14:04 GMT+01:00 Sanne Grinovero : > On 13 December 2017 at 13:54, Steve Ebersole wrote: > > Considering the spec

Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-13 Thread Sanne Grinovero
On 13 December 2017 at 13:54, Steve Ebersole wrote: > Considering the spec contracts are defined by the EG under the JCP, I'm not > sure where we ever stood legally with publishing this under any other > license. Either way, I am not concerned about the license aspect - I

Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-13 Thread Steve Ebersole
Considering the spec contracts are defined by the EG under the JCP, I'm not sure where we ever stood legally with publishing this under any other license. Either way, I am not concerned about the license aspect - I think it is a reasonable expectation that if I am using a jar produced by a spec

Re: [hibernate-dev] Killing hibernate-jpa-api ?

2017-12-13 Thread Yoann Rodiere
Seems like the right thing to do. I'm just concerned about the license. Is it identical? Some people might be upset to get a new dependency pulled "automatically" if it has a stricter license... Yoann Rodière Hibernate NoORM Team yo...@hibernate.org On 13 December 2017 at 13:10, Sanne Grinovero

[hibernate-dev] Killing hibernate-jpa-api ?

2017-12-13 Thread Sanne Grinovero
Looks like the general agreement is that we will no longer need - https://github.com/hibernate/hibernate-jpa-api As we're switching to the standard API distribution, finally available: javax.persistence:javax.persistence-api:2.2 Still I expect there's going to be some confusion about this, e.g.