No worries, we can get out another fix version rather soon. Let's say in about a month?
LieGrue, strub > Am 23.04.2019 um 10:19 schrieb Michael Wiles <michael.wi...@gmail.com>: > > Hi all... > > Just a heads up - I thought you might want to know. > > I've found a fairly significant issue with 3.1.0... > > In a nutshell... you can't use anonymous parameters via the criteria api... > https://issues.apache.org/jira/browse/OPENJPA-2788 > > It was picked up by how spring data was using jpa but then as you can see, > I created a test independent of spring data... > > It seems the fix for the previous problem with startup on spring data broke > the hashCode and equals semantics for anonymous parameters - parameters > without names all resolve to the same parameter... > > I'm very sorry about this as I was keen to upgrade to 3.1.0 and see what > new features I can now use, but this issue causes my spring data queries to > fail so I can't upgrade until this is addressed. > > I'll try take a closer look if I get some time. > > Michael > > > > On Tue, 23 Apr 2019 at 06:05, Maxim Solodovnik <solomax...@gmail.com> wrote: > >> It seems I get some slow repositories, SNAPSHOTs are being checked >> "forever" :( >> Will try to review my global Maven settings to speed everything up :) >> >> On Mon, 22 Apr 2019 at 21:08, Romain Manni-Bucau <rmannibu...@gmail.com> >> wrote: >>> >>> Maybe you have a mirror? >>> >>> Le lun. 22 avr. 2019 à 14:54, Maxim Solodovnik <solomax...@gmail.com> a >>> écrit : >>> >>>> Thanks Romain, >>>> >>>> sorry for the noise >>>> for whatever reason `mvn versions:display-property-updates` doesn't >>>> display openjpa was updated :( >>>> >>>> On Mon, 22 Apr 2019 at 18:14, Romain Manni-Bucau < >> rmannibu...@gmail.com> >>>> wrote: >>>>> >>>>> Hi Maxim >>>>> >>>>> It is already available, dont get abused by websites on top of >> central >>>> like >>>>> mvnrepository or others, these are not the source of truth. >>>>> >>>>> >>>>> Le lun. 22 avr. 2019 à 12:39, Maxim Solodovnik <solomax...@gmail.com> >> a >>>>> écrit : >>>>> >>>>>> Hello Mark, >>>>>> >>>>>> When are you planning to push this release to maven? >>>>>> >>>>>> On Sun, 14 Apr 2019 at 03:43, Mark Struberg >> <strub...@yahoo.de.invalid >>>>> >>>>>> wrote: >>>>>>> >>>>>>> Hi folks! >>>>>>> >>>>>>> And with my own +1 I can conclude: >>>>>>> >>>>>>> The VOTE did pass with the following: >>>>>>> >>>>>>> +1: Romain, Francesco, Maxim, Jon, Michael, Mark >>>>>>> no -1 nor 0. >>>>>>> >>>>>>> txs 2 all who reviewed and voted! >>>>>>> >>>>>>> I'll gonna continue with the release process. >>>>>>> >>>>>>> LieGrue, >>>>>>> strub >>>>>>> >>>>>>> >>>>>>> >>>>>>>> Am 10.04.2019 um 22:25 schrieb Mark Struberg >>>> <strub...@yahoo.de.INVALID >>>>>>> : >>>>>>>> >>>>>>>> hi folks! >>>>>>>> >>>>>>>> 2nd take after fixing the ParameterExpression equals. >>>>>>>> >>>>>>>> We have fixed tons of enhancements and bugs in OpenJPA for our >>>> 3.1.0 >>>>>> release. >>>>>>>> One of the main improvements is to move to a native JavaEE8 >> level - >>>>>> JPA-2.2. >>>>>>>> Please note that we implemented many JPA-2.2 features but not >> all >>>> yet. >>>>>>>> We will work towards implementing the rest of the missing 2.2 >>>> stuff in >>>>>> the next bugfix releases. >>>>>>>> >>>>>>>> >>>>>>>> Here are the fixed tickets: >>>>>>>> >>>>>>>> Sub-task >>>>>>>> • [OPENJPA-2710] - Create and update to >> geronimo-jpa_2.2_spec >>>>>>>> >>>>>>>> Bug >>>>>>>> • [OPENJPA-1993] - Deadlock Potential with ORM XML >> Processing >>>>>>>> • [OPENJPA-2555] - Timestamp precision from manual >> schema not >>>>>> respected >>>>>>>> • [OPENJPA-2567] - TINY/MEDIUM/LONG TEXT fields for >> MySQL and >>>>>> MariaDB are not supported >>>>>>>> • [OPENJPA-2673] - Table is not created in openjpa >>>>>> 3.0.0-SNAPSHOT and OSGi >>>>>>>> • [OPENJPA-2704] - The openjpa.jdbc.Schema no longer >>>> overrides >>>>>> orm.xml default >>>>>>>> • [OPENJPA-2733] - Subquery parameters are incorrectly >>>> assigned >>>>>>>> • [OPENJPA-2742] - SchemaTool fails with MySQL >>>>>>>> • [OPENJPA-2746] - OpenJPA Karaf feature is not complete >>>>>>>> • [OPENJPA-2756] - PostgreSQL requires escaping of search >>>>>> strings in all versions >>>>>>>> • [OPENJPA-2757] - upgrade to xbean-asm7 to support >> Java11 >>>>>>>> • [OPENJPA-2761] - problem inserting more than 4000 >>>> charcters in >>>>>> oracle XMLTYPE column >>>>>>>> • [OPENJPA-2764] - Map path expression tests behave >> random >>>>>>>> • [OPENJPA-2768] - XMLStore SAXParser doesn't distinguish >>>>>> between element and extent >>>>>>>> • [OPENJPA-2770] - false boolean literal doesn't work >>>>>>>> • [OPENJPA-2771] - It seems like h2 'unlimited' is not >>>> "LIMIT 0" >>>>>> but rather "LIMIT -1" >>>>>>>> • [OPENJPA-2772] - list of h2 reserved words is >> incomplete >>>>>>>> • [OPENJPA-2777] - Indices specified using >>>>>> javax.persistence.Index annotation are not being created >>>>>>>> • [OPENJPA-2780] - ReverseMappingTool does not generate >>>>>> @Enumerated annotation >>>>>>>> • [OPENJPA-2781] - OpenJPA need internet connection to >> read >>>> the >>>>>> persistence.xml >>>>>>>> • [OPENJPA-2785] - Queries invoked by Spring data that >> have >>>>>> parameters fail >>>>>>>> >>>>>>>> Improvement >>>>>>>> • [OPENJPA-2745] - Clean up try-catch implementation for >>>>>> DB2Dictionary >>>>>>>> • [OPENJPA-2747] - Upgrade to JPA 2.2 and use >>>>>> javax.persistence-api spec >>>>>>>> • [OPENJPA-2748] - commons-collections should be updated >> to >>>> most >>>>>> recent version >>>>>>>> • [OPENJPA-2750] - commons-dbcp need to be updated to >> most >>>>>> recent version >>>>>>>> • [OPENJPA-2751] - Code clean-up should be performed >>>>>>>> • [OPENJPA-2752] - More libraries can be updated >>>>>>>> • [OPENJPA-2753] - Create profiles to start various >> databases >>>>>> via Docker >>>>>>>> • [OPENJPA-2755] - support MySQL DATETIME and TIMESTAMP >>>>>> fractions (milliseconds, nanos) >>>>>>>> • [OPENJPA-2773] - set minIdle to > 0 in >> DBCPDriverDataSource >>>>>>>> • [OPENJPA-2775] - hsqldb doesn't support NullTable to >>>> retrieve >>>>>> meta information >>>>>>>> >>>>>>>> Task >>>>>>>> • [OPENJPA-2744] - commons-pool should be updated to most >>>> recent >>>>>> version >>>>>>>> • [OPENJPA-2754] - update to latest dbcp and verify >> moving >>>> from >>>>>> maxActive to maxTotal >>>>>>>> • [OPENJPA-2758] - JPA 2.2 compliance >>>>>>>> >>>>>>>> Dependency upgrade >>>>>>>> • [OPENJPA-2784] - update docs before our release >>>>>>>> >>>>>>>> The staging repository is at: >>>>>>>> >>>>>> >>>> >> https://repository.apache.org/content/repositories/orgapacheopenjpa-1006/ >>>>>>>> >>>>>>>> The source release is at >>>>>>>> >>>>>> >>>> >> https://repository.apache.org/content/repositories/orgapacheopenjpa-1006/org/apache/openjpa/openjpa-parent/3.1.0/ >>>>>>>> sha1 is ccfeb1b83518347f46113bb866027eb7996614f7 >>>>>>>> >>>>>>>> I've pushed the release branch to my github repo >>>>>>>> https://github.com/struberg/openjpa/tree/release-3.1.0 >>>>>>>> >>>>>>>> >>>>>>>> Please VOTE: >>>>>>>> >>>>>>>> [+1] yeah, ship it! >>>>>>>> [+0] meh, don't care >>>>>>>> [-1] nah, because ${showstopper} >>>>>>>> >>>>>>>> The VOTE is open for 72h >>>>>>>> >>>>>>>> txs and LieGrue, >>>>>>>> strub >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> WBR >>>>>> Maxim aka solomax >>>>>> >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax >>>> >> >> >> >> -- >> WBR >> Maxim aka solomax >> > > > -- > see my blog: > http://analysis102.blogspot.com > http://audiblethoughts.blogspot.com > http://outsideofficehours.blogspot.com
