Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId

2017-02-02 Thread Steve Ebersole
https://hibernate.atlassian.net/browse/HHH-11444 On Tue, Jan 31, 2017 at 12:52 AM Christian Beikov < christian.bei...@gmail.com> wrote: > Sounds good to me. +1 > > Am 30.01.2017 um 17:31 schrieb Steve Ebersole: > > Relatedly, I have been thinking whether we want to rename the ORM > artifacts > >

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-02-01 Thread Steve Ebersole
Good points Gunnar. So then we'll plan to rename hibernate-core to hibernate-orm and the others from hibernate-{module} to hibernate-orm-{module}. On Tue, Jan 31, 2017 at 2:09 AM Gunnar Morling wrote: > Agreed, it'd be the right time if we wanted to change this. > > I vote for 1 in case we do

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-02-01 Thread Steve Ebersole
The underlying problem is still unfixed[1]. There is a work around we could try. [1] https://issues.gradle.org/browse/GRADLE-2966 -> https://github.com/gradle/gradle/issues/1061 On Wed, Feb 1, 2017 at 11:43 AM Steve Ebersole wrote: > Most likely it is the cycle between hibernate-core and > hi

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-02-01 Thread Steve Ebersole
Most likely it is the cycle between hibernate-core and hibernate-orm-modules. Let me research a bit... On Tue, Jan 31, 2017 at 2:34 PM andrea boriero wrote: > rebased my old PR and it stops working, the "publishing is not yet able to > resolve a dependency on a project with multiple different

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-01-31 Thread andrea boriero
rebased my old PR and it stops working, the "publishing is not yet able to resolve a dependency on a project with multiple different publications" exception is back :( I'm investigating to understand what change reintroduced this issue. On 31 January 2017 at 09:57, andrea boriero wrote: > after

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-01-31 Thread andrea boriero
after thinking a bit on +1 for Steve proposal On 31 January 2017 at 08:09, Gunnar Morling wrote: > Agreed, it'd be the right time if we wanted to change this. > > I vote for 1 in case we do it. > > In ORM it's enough for many use cases to just add that core module, > hence I like the more concis

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-01-31 Thread Gunnar Morling
Agreed, it'd be the right time if we wanted to change this. I vote for 1 in case we do it. In ORM it's enough for many use cases to just add that core module, hence I like the more concise "hibernate-orm" id (similar to "hibernate-validator"). It's a bit different for OGM and HSEARCH where one ne

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId

2017-01-30 Thread Christian Beikov
Sounds good to me. +1 Am 30.01.2017 um 17:31 schrieb Steve Ebersole: > Relatedly, I have been thinking whether we want to rename the ORM artifacts > as well since this is the best time if we wanted to do that. > > So we know we will change the groupId to `org.hibernate.orm`. > > I was thinking we

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-01-30 Thread andrea boriero
Not have a strong opinion on the renaming. On 30 Jan 2017 19:05, "andrea boriero" wrote: I worked on the ORM relocation script probably a year ago, I'll have to go back and refresh my memory. Tomorrow I'll give a look at it. On 30 Jan 2017 16:44, "Steve Ebersole" wrote: > Relatedly, I have be

Re: [hibernate-dev] Hibernate ORM 6.0 groupId/artifactId (was: Re: NoORM - New groupId and relocation artifacts)

2017-01-30 Thread andrea boriero
I worked on the ORM relocation script probably a year ago, I'll have to go back and refresh my memory. Tomorrow I'll give a look at it. On 30 Jan 2017 16:44, "Steve Ebersole" wrote: > Relatedly, I have been thinking whether we want to rename the ORM artifacts > as well since this is the best tim