First... Welcome Michael! I'm excited to have some fresh blood on the project. Sounds like you are ready to jump in.
Are you planning on making changes to the 1.x line, or are you planning all this work in the 3.x line? Is your goal backward compatibility or a 1.x release marking breaks as deprecated?
Do you have list of Java features you are suggesting?
My list:
Upgrade to nUnit 2.5 (breaking changes)
Include nUnit in externals-bin and reference it there so we control what version is used and it is consistent
Allow for a nullable column(s) check to see if an object is even created for N+1 selects
Allow for a column prefix when defining groupBy and resultMap so you can reuse resultMaps
Mike
On Mon, Jun 22, 2009 at 8:28 AM, Michael McCurrey
<mmccurrey@...> wrote:
Ok folks,
I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are:
1. Feature match the Java version
2. Fix an annoying list non lazy load bug
3. Rev to my Castle.DynamicProxy2 patch
4. Expose a QueryForDataTable
5. Drop .net 1.X compatibility.
6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front.
--
Michael
