You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by Donald Woods <dw...@apache.org> on 2009/02/03 19:37:09 UTC
Plans for a OpenJPA 1.2.1 release?
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
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Michael Dick <mi...@gmail.com>.
Thanks for the explanation, I haven't been following the OpenEJB mailing
list so it was a surprise to me. In case they are related to the
1.2.1-SNAPSHOT I'll hold off on the release (at least until we're
exonerated).
-mike
On Tue, Feb 3, 2009 at 4:20 PM, Kevin Sutter <kw...@gmail.com> wrote:
> Mike,
> IIRC, the TCK failures were actually in the EJB bucket, not the JPA bucket.
> That's why OpenEJB was hitting the problem and we weren't.
>
> Kevin
>
> On Tue, Feb 3, 2009 at 4:05 PM, Michael Dick <michael.d.dick@gmail.com
> >wrote:
>
> > I ran the TCK in isolation earlier today and there are no failures that
> I'm
> > aware of. I'm using the tck configuration from the openjpa source tree in
> > case that makes a difference.
> >
> > Donald, which svn revision do you have that sees the TCK issues?
> > OPENJPA-872
> > should have been fixed in revision728758 under OPENJPA-838..
> >
> > -mike
> >
> > On Tue, Feb 3, 2009 at 2:48 PM, Kevin Sutter <kw...@gmail.com> wrote:
> >
> > > 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 <dw...@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 <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
> > > >>>
> > > >>>
> > > >>
> > >
> >
>
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Kevin Sutter <kw...@gmail.com>.
Mike,
IIRC, the TCK failures were actually in the EJB bucket, not the JPA bucket.
That's why OpenEJB was hitting the problem and we weren't.
Kevin
On Tue, Feb 3, 2009 at 4:05 PM, Michael Dick <mi...@gmail.com>wrote:
> I ran the TCK in isolation earlier today and there are no failures that I'm
> aware of. I'm using the tck configuration from the openjpa source tree in
> case that makes a difference.
>
> Donald, which svn revision do you have that sees the TCK issues?
> OPENJPA-872
> should have been fixed in revision728758 under OPENJPA-838..
>
> -mike
>
> On Tue, Feb 3, 2009 at 2:48 PM, Kevin Sutter <kw...@gmail.com> wrote:
>
> > 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 <dw...@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 <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
> > >>>
> > >>>
> > >>
> >
>
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Michael Dick <mi...@gmail.com>.
I ran the TCK in isolation earlier today and there are no failures that I'm
aware of. I'm using the tck configuration from the openjpa source tree in
case that makes a difference.
Donald, which svn revision do you have that sees the TCK issues? OPENJPA-872
should have been fixed in revision728758 under OPENJPA-838..
-mike
On Tue, Feb 3, 2009 at 2:48 PM, Kevin Sutter <kw...@gmail.com> wrote:
> 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 <dw...@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 <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
> >>>
> >>>
> >>
>
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Kevin Sutter <kw...@gmail.com>.
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 <dw...@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 <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
>>>
>>>
>>
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Donald Woods <dw...@apache.org>.
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 <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
>>
>
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Donald Woods <dw...@apache.org>.
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 <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
>>
>
Re: Plans for a OpenJPA 1.2.1 release?
Posted by Michael Dick <mi...@gmail.com>.
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
>