Hi Jean-Baptiste, I'll take a look at the patch, but I don't have a plan to target this fix for 1.2.2 (I'm trying to close down the branch to prepare for a release), it might might 1.2.3.
In the mean time I can add it to 1.3.0-SNAPSHOT, and look into doing a 1.3.0 release (probably after 1.2.2). Regards, -mike On Wed, Jan 6, 2010 at 3:32 AM, Jean-Baptiste BRIAUD -- Novlog < [email protected]> wrote: > That fix is in the trunk, will it be in the 1.2.2 branch ? > > On Jan 5, 2010, at 09:26 , Jean-Baptiste BRIAUD -- Novlog wrote: > > > Thanks a lot. > > Unfortunately, I'm afraid the trunk would be too risky for production, > isn't it ? > > That problem is now corrected in the trunk but I'll probably found new > problem ? > > > > What do you think ? > > > > On Jan 4, 2010, at 22:21 , Fay Wang wrote: > > > >> Hi, > >> I have checked in the fix and the test case for this problem in the > trunk. > >> > >> Regards, > >> Fay > >> > >> > >> > >> ----- Original Message ---- > >> From: Jean-Baptiste BRIAUD -- Novlog <[email protected]> > >> To: [email protected] > >> Sent: Mon, January 4, 2010 4:43:59 AM > >> Subject: Re: PersistentCollection bug. OpenJPA version to use. > >> > >> Any advices on that one ? > >> > >> On Dec 30, 2009, at 12:24 , Jean-Baptiste BRIAUD -- Novlog wrote: > >> > >>> Hi, > >>> > >>> I'm facing a ClassCastException in the context of a > PersistentCollection. > >>> > >>> It sound like exactly the behavior described here : > >>> http://issues.apache.org/jira/browse/OPENJPA-1020 > >>> > >>> This bug look like fix but without any OpenJPA fix version. > >>> > >>> Any news ? > >>> > >>> I'm using a 1.2.2 snapshot from september. > >>> I noticed last snapshot (according to system date) is from december. > >>> > http://people.apache.org/repo/m2-snapshot-repository/org/apache/openjpa/apache-openjpa/1.2.2-SNAPSHOT/ > >>> > >>> Is there any interest for us to upgrade the snapshot from september's > one to current one ? > >>> If yes, what is the difference between snapshot and nightly build then > ? > >>> > >>> I tested the 1.2.2. snapshot from 17th of decembre : nothing changed, > the bug is still there. > >>> > >>> We are in a delivery phase for a customer, so I think I should not use > 2.0 since there are too much changes. > >>> > >>> Any idea, advices ? > >>> > >>> Thanks. > >>> > >>> > >> > >> > >> > >> > >> > > > > > >
