I fixed the problem on the 2.0.X branch. Not sure if that was the right place to do it, but it's done.
I created this issue when I worked on some tickets for the 2.0.10 release. At the time I overlooked the fact that it was a protected method and I was changing the API. My bad. Everything should be all set now for another release roll. Do I need to move everything in JIRA to 2.0.12 now? James On Mon Sep 17 8:52 , 'Ted Husted' <[EMAIL PROTECTED]> sent: >On 9/17/07, Antonio Petrelli [EMAIL PROTECTED]> wrote: >> I am -1 to retagging, since the JAR already went out to the public, and it >> will be a mess for the support. As Wendy (Smoak) said, what happens when >> someone asks support for 2.0.10? "Which 2.0.10 have you got?" > >It would be just as easy to go onto 2.0.11. But, in any event, nothing >different is happening unless someone looks into a patch. I'll be >offline the rest of the day, but I'll checkin tonight, in case we want >to roll another 2.0.10 or 2.0.11. > >-Ted. > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
