AndCooper IDe and ease of use

One of the challenges of development of the AndCooper of Android application development tool is IDE and ANT interactions. For example, to asy you a typical construction system based on ANT. How many of these ant taskdef libraries you have to put in your Ant IDE path parameter?

If you guess all you would be a little wrong and would have a generation that in would not work as expected. In the case AndCooper its 12 including the taskdef ant from the Android SDK libraries. The idea is once AndCooper is installed, you can point your java IDE configuration generator to use the AndCooper of build scripts like java for the project generator so that you develop the code the IDE uses AndCooper to build the project in increments and generate reports of data into a single company code analysis to facilitate the development process.

So, its essential that I get Ant taskdef libraries put on the path of the correct IDE Ant so the AndCooper user can go right into the code with AndCooper development. The chance is that every IDE appears to accept that you must load the same subset of libraries on the classpath from Ant IDE taskdef.

View the original article here