Re: Is it time for 3.0.1 release?

+1 for a release, 3.1.0 sounds good to me too Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

[jira] [Commented] (OPENJPA-2777) Indices specified using javax.persistence.Index annotation are not being created

[ https://issues.apache.org/jira/browse/OPENJPA-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784447#comment-16784447 ] ASF subversion and git services commented on OPENJPA-2777: -- Commit

Re: Is it time for 3.0.1 release?

Hi Mark, huge +1 for rolling a release - thanks for all your work. 3.1.0 would make sense, due to the API-level change - even though I don't think we'll ever release 3.0.1 with JPA 2.1, anyway... Regards. On 05/03/19 14:44, Mark Struberg wrote: One more question: What about the version? [ ]

Re: Is it time for 3.0.1 release?

3.1.0 sound more reasonable to me On Tue, 5 Mar 2019 at 20:44, Mark Struberg wrote: > > > One more question: > What about the version? > [ ] 3.0.1 or[ ] 3.1.0 as we updated the spec-api version? > LieGrue,strub > On Tuesday, 5 March 2019, 14:40:21 CET, Mark Struberg > wrote: > > We now

[jira] [Resolved] (OPENJPA-2777) Indices specified using javax.persistence.Index annotation are not being created

[ https://issues.apache.org/jira/browse/OPENJPA-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Solodovnik resolved OPENJPA-2777. --- Resolution: Fixed > Indices specified using javax.persistence.Index annotation are

Re: Is it time for 3.0.1 release?

One more question: What about the version? [ ] 3.0.1 or[ ] 3.1.0 as we updated the spec-api version? LieGrue,strub  On Tuesday, 5 March 2019, 14:40:21 CET, Mark Struberg wrote: We now have the official JPA-2.2 api jar. Our internal tests do pass. There are surely a few more bugs to

Re: Is it time for 3.0.1 release?

We now have the official JPA-2.2 api jar. Our internal tests do pass. There are surely a few more bugs to fix, but I'd say we can now do a release and focus on further bugfixes and more jpa-2.2 features later. wdyt? LieGrue,strub On Wednesday, 20 February 2019, 08:01:46 CET, Francesco

[jira] [Commented] (OPENJPA-2747) Upgrade to JPA 2.2 and use javax.persistence-api spec

[ https://issues.apache.org/jira/browse/OPENJPA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784425#comment-16784425 ] ASF subversion and git services commented on OPENJPA-2747: -- Commit

[jira] [Work logged] (OPENJPA-2747) Upgrade to JPA 2.2 and use javax.persistence-api spec

[ https://issues.apache.org/jira/browse/OPENJPA-2747?focusedWorklogId=207780=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-207780 ] ASF GitHub Bot logged work on OPENJPA-2747: --- Author: ASF GitHub Bot

[jira] [Resolved] (OPENJPA-2747) Upgrade to JPA 2.2 and use javax.persistence-api spec

[ https://issues.apache.org/jira/browse/OPENJPA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved OPENJPA-2747. - Resolution: Fixed > Upgrade to JPA 2.2 and use javax.persistence-api

[jira] [Resolved] (OPENJPA-2758) JPA 2.2 compliance

[ https://issues.apache.org/jira/browse/OPENJPA-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Struberg resolved OPENJPA-2758. Resolution: Fixed Assignee: Mark Struberg Fix Version/s: 3.0.1 txs for