You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Donald Woods <dw...@apache.org> on 2009/02/03 20:09:37 UTC

[Fwd: Re: Plans for a OpenJPA 1.2.1 release?]


-------- Original Message --------
Subject: Re: Plans for a OpenJPA 1.2.1 release?
Date: Tue, 3 Feb 2009 13:02:53 -0600
From: Michael Dick <mi...@gmail.com>
Reply-To: dev@openjpa.apache.org
To: dev@openjpa.apache.org
References: <49...@apache.org>

Hi Donald,

I'm looking into this at the moment. I need to do some JIRA issue cleanup (I
suspect) but I'll try to get the branch created later tonight.

-mike

On Tue, Feb 3, 2009 at 12:37 PM, Donald Woods <dw...@apache.org> wrote:

> Have we started planning a OpenJPA 1.2.1 release?  The upcoming Geronimo
> 2.1.4 release would like to include an updated OpenJPA release due to the
> issue mentioned below.
>
>
> Thanks,
> Donald
>
>
> -------- Original Message --------
>
>
> On Jan 27, 2009, at 11:39 AM, Donald Woods wrote:
>
>  Do we need to upgrade to OpenJPA 1.2.1-SNAPSHOT and approach the OpenJPA
>> team for a release, based on the resolution in -
>>
>> https://issues.apache.org/jira/browse/OPENJPA-872
>>
>
> Yes. I'm in the process of sending them a note...
>
> Looks like we could consider using <property
> name="openjpa.jdbc.QuerySQLCache" value="false"/> to work-around the
> problem, if necessary.
>
> --kevan
>