This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: The Why of Orca TDD Build Framework
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
Why create Orca TDD Build Framewokr for J2me developers? One, 90% of J2ME developers or groups or companies are under 10 developers or less. In that realm alone you need to increase code analysis, metrics, and etc to work aorund the imperfections of J2ME implementations amoung SUN and OEMs.
The QA improvements SUN has made now take time to work themselves down to OEMS and it takes time for those devices with those changes to saturate the market and currently devices cannot update thier J2mE environment. THUs, we are faced with handling legacy J2ME imperfect implementations and even 5 years waya there will be some percentage of those devices in the market place.
Since we cannot control the implmenetation thna we have to ramp up the feedback via code metrics, code analysis for code review, and etc in an automatic way that can be run by one developer with easy configuration. Thus, the need for the ORCA TDD Build Framework.
What about a href="http://research.sun.com/projects/jackpot/">Sun's Jackpot? Jackpot has a different strategy and different goals for a tool for J2SE and J2ee develolprs and quite frankly the J2ME developer process has large parts of that process that are vasty differnt from J2SE/J2EE development.
Orca TDD Build Framework is inteneded to be IDE non centric running either from ANT or IDE+ANT and is focused on being FOSS licensed for all j2me devlopers no matter if they are open source, free source, or closed source.
Previous Topic
