Sorry, I forgot to mention this sooner... It's a minor recommendation for your own sanity.
I suggest avoiding the reverse title case used by iBATIS... It's a decision I wish I hadn't made. I would suggest simply using Ibator or even better: ibator. In hindsight, I wish I had used all lowercase: ibatis. It might also look better and be easier to read when written in its full form: Apache iBATIS ibator. While unique, it presents a lot of challenges in typing, naming, and general writing. Totally your call though. Other than that, I love the new name, despite the reason for the change. :-) Congratulations again on building a kick ass product that is gathering attention of all kinds. Cheers, Clinton On Tue, Apr 15, 2008 at 12:04 AM, Jeff Butler <[EMAIL PROTECTED]> wrote: > Due to a trade registration dispute, we are renaming Apache iBATIS Abator > to Apache iBATIS iBATOR. > > The new version is still under development - although the core work is > almost complete. I have committed an initial version to SVN so you can take > a look at what's going on. There will be no further enhancements or changes > to Abator - all new work will be in the iBATOR code stream here: > http://svn.apache.org/repos/asf/ibatis/trunk/java/tools/ibator/. > > I will be focusing on some changes to the Eclipse plugin for the new few > weeks before doing a formal release. The new version will NOT be 100% > compatible with Abator - but will be very close. Transition from Abator to > iBATOR should be simple. I've listed some information about the development > effort on the iBATOR homepage (http://ibatis.apache.org/ibator.html) if > you want more information. > > This would be a good time to make suggestions for improvements to iBATOR > as I am willing to make some breaking changes with the new version - so feel > free to let me know if there are things you would like to see added or > changed. BTW - I know there is some interest about seeing table > relationships handled in iBATOR. This will not make it into the initial > release. It's a big job, and I'm still not convinced of the usefulness of > doing this. > > I hope to keep the disruption to a minimum, and I will include a migration > guide once the new version is complete. Let me know if you have any good > ideas for the future of iBATOR. > > Jeff Butler > >
