[hibernate-dev] OGM at Soft Shake

2013-07-26 Thread Guillaume SCHEIBEL
Hi guys, I'm glad to announce/let you know I'll be presenting OGM at Soft Shake (Geneva, Switzerland) in October. Cheers Guillaume ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] OGM at Soft Shake

2013-07-26 Thread Sanne Grinovero
Congratulations! Good job, Sanne On 26 July 2013 13:36, Guillaume SCHEIBEL wrote: > Hi guys, > > I'm glad to announce/let you know I'll be presenting OGM at Soft Shake > (Geneva, Switzerland) in October. > > > Cheers > Guillaume > ___ > hibernate-dev m

Re: [hibernate-dev] OGM at Soft Shake

2013-07-26 Thread Davide D'Alto
Great job, Davide On Fri, Jul 26, 2013 at 2:36 PM, Guillaume SCHEIBEL < guillaume.schei...@gmail.com> wrote: > Hi guys, > > I'm glad to announce/let you know I'll be presenting OGM at Soft Shake > (Geneva, Switzerland) in October. > > > Cheers > Guillaume >

[hibernate-dev] JPA API jar

2013-07-26 Thread Steve Ebersole
I just released the "Final" JPA API jar. It is still using the old naming scheme in terms of repo artifacts; so this one is: groupId : org.hibernate.javax.persistence artifactId : hibernate-jpa-2.1-api version : 1.0.0.Final I think moving forward we will move to a slightly different scheme. The

Re: [hibernate-dev] JPA API jar

2013-07-26 Thread Hardy Ferentschik
On 26 Jan 2013, at 7:26 PM, Steve Ebersole wrote: > I just released the "Final" JPA API jar. It is still using the old > naming scheme in terms of repo artifacts; so this one is: > > groupId : org.hibernate.javax.persistence > artifactId : hibernate-jpa-2.1-api > version : 1.0.0.Final nice

Re: [hibernate-dev] JPA API jar

2013-07-26 Thread Steve Ebersole
Well the problem comes up in versions like '1.0.0.Draft-7plus', which was Draft-7 + some stuff we had just discussed in the EG. Or what about cases where we are combining work from a few drafts? All in all, its not great. What I was thinking instead is to use Alpha/Beta/CR and in the Jira no

Re: [hibernate-dev] JPA API jar

2013-07-26 Thread Sanne Grinovero
On 26 July 2013 18:51, Hardy Ferentschik wrote: > > On 26 Jan 2013, at 7:26 PM, Steve Ebersole wrote: > >> I just released the "Final" JPA API jar. It is still using the old >> naming scheme in terms of repo artifacts; so this one is: >> >> groupId : org.hibernate.javax.persistence >> artifactId

Re: [hibernate-dev] JPA API jar

2013-07-26 Thread Steve Ebersole
I do not agree with needing to see this in the artifact name. I can see putting it in the metadata (pom, manifest, etc) in addition to Jira. 'draft' does in deed fit into the chronology scheme defined by JBoss. Except that 'draft' is not defined as a valid value. Here is another thing to cons