openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sutter <kwsut...@gmail.com>
Subject Re: Plans for a OpenJPA 1.2.1 release?
Date Tue, 03 Feb 2009 20:48:29 GMT
I thought the TCK failures were tracked down to OPENJPA-872 and that has
been resolved.  Thus, a 1.2.1 release is what the "doctor" was asking
for...

Kevin

On Tue, Feb 3, 2009 at 2:02 PM, Donald Woods <dwoods@apache.org> wrote:

> Actually, looks like we may still have 2 TCK tests that are failing with
> OpenJPA 1.2.0/1.2.1-SNAPSHOT, that pass if we rollback to the 1.0.3 release,
> so let's put creating that branch on hold until we can further debug the
> failures we are seeing.
>
>
> Thanks,
> Donald
>
>
>
> Michael Dick wrote:
>
>> 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 <dwoods@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
>>>
>>>
>>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message