Re: [hibernate-dev] Hibernate ORM modules published as major.minor and an alias for main

> On 16 Jan 2015, at 13:58, Sanne Grinovero wrote: > > On 15 January 2015 at 16:01, Emmanuel Bernard > wrote: >> >> On 15 Jan 2015, at 16:54, Scott Marlow wrote: >> >> >> The part that I am unsure about is including the micro version in the module >> path, whi

Re: [hibernate-dev] Hibernate ORM modules published as major.minor and an alias for main

On 15 January 2015 at 16:01, Emmanuel Bernard wrote: > > On 15 Jan 2015, at 16:54, Scott Marlow wrote: > > > The part that I am unsure about is including the micro version in the module > path, which means that every release of WildFly that includes an upgraded > Hibernate, will likely have the j

Re: [hibernate-dev] Hibernate ORM modules published as major.minor and an alias for main

> On 15 Jan 2015, at 16:54, Scott Marlow wrote: > > > The part that I am unsure about is including the micro version in the module > path, which means that every release of WildFly that includes an upgraded > Hibernate, will likely have the jars in a different path (could be a pain for > any

Re: [hibernate-dev] Hibernate ORM modules published as major.minor and an alias for main

On 01/15/2015 09:49 AM, Emmanuel Bernard wrote: > >> On 15 Jan 2015, at 14:56, Scott Marlow > > wrote: >> >> When we talked at the f2f, I said that we would do major.minor, I think >> that is the summary notes from the discussion. >> >> If we were to reverse the definitio

Re: [hibernate-dev] Hibernate ORM modules published as major.minor and an alias for main

> On 15 Jan 2015, at 14:56, Scott Marlow wrote: > > When we talked at the f2f, I said that we would do major.minor, I think > that is the summary notes from the discussion. > > If we were to reverse the definitions, so that org.hibernate:main is an > alias for a specific version of ORM (wheth