No. The Spring integration is using internals of iBATIS which are not meant to be publicly consumed. We're not going to stop evolving our code just to keep compatible with 3rd party frameworks that reach into the guts of iBATIS. Waiting for 2.4 would just delay the inevitable.
The solutions is: * Update the Spring plug-in, and * Use 2.3.0 until it is updated. This doesn't happen every day. In fact it's the first time it's happened in 4 years. Let's not make it out to be more of an issue than it is. Spring will be updated and all will be well. Clinton On Thu, Jul 17, 2008 at 7:34 AM, Dragan Jotanovic < [EMAIL PROTECTED]> wrote: > Upgrading to newer version of iBatis is becoming more and more > complicated. > > So now we will have to wait for new version of spring in order to get new > version of iBatis? Isn't it better just to revert all those changes back on > branch 2.3.x and start new branch with those changes (2.4 or long waiting > 3.0)? > > > > > > *From:* Clinton Begin [mailto:[EMAIL PROTECTED] > *Sent:* Thursday, July 17, 2008 2:21 PM > *To:* [email protected] > *Subject:* Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production > > > > Wooooow... > > K, it's looking more and more like we just need to update the Spring > integration. I'm not willing to roll back all of the simplifications we > made to the software. We got rid of a lot of internal cruft that just made > the code harder to read and didn't serve a purpose. > > I'll see what I can do to work with the Spring team to get it updated. I > no longer consider this a bug, it's an evolution. > > Clinton > > On Thu, Jul 17, 2008 at 4:16 AM, Iwao AVE! <[EMAIL PROTECTED]> wrote: > > Hi Clinton, > > I understand you need more testers, but then, why don't you publish these > betas in the maven repository? > It would increase the number of testers (1 at least = me). > > Sorry if this topic has been discussed already. > > Regards, > Iwao > > >
