This post originated from an RSS feed registered with Java Buzz by Fred Grott. Original Post: AndCooper IDe and useability 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. Latest Java Buzz Posts Latest Java Buzz Posts by Fred Grott Latest Posts From ShareMe Technologies LLC-The Mobile Future

One of the challenges of developing the AndCooper build tool of Android application development is the IDE and ANT interactions. For example, lets asy you have a typical build system based on ANT. How many of those ant taskdef  libraries do you have to put in your IDE ant path setting?

If you guess all of them you would be somewhat wrong and would have a build that at would not work as expected. In the AndCooper case its 12 including the ant taskdef libraries from the Android SDK. The whole idea is once AndCooper is installed you can point your IDE java builder setting to use the AndCooper set of build scripts as the java builder for that project so as you develop code the IDE will use AndCooper to build the project in increments and generate soem code analysis data reports to assist in the development process.

Thus, its vital that I get which ant taskdef libraries to put on the IDE ant path correct so the user of AndCooper can jump right into developing code with AndCooper. The lucky part is that each IDE seems to accept that you must load the same subset of taskdef libraries on the IDE ant classpath.