Geek Answers Handbook

Updated to 2.3, now ant builds do not include bans in my libs directory

I did all my builds with ant on the command line (Ubuntu 10.04). I downloaded the 2.3 SDK and changed the required path (platform tools). Now my assemblies do not contain jars in my libs directory. Any thoughts on what I need to change?

+4
source share
3 answers

Now Ant build system requires Ant 1.8+ Unfortunately, it "works" (broken) since 1.7, because we rely on the new behavior in version 1.8, and not on a new task or attribute that would break 1.7

+6
source

I am not familiar with the ant construct for android, since I am uscl eclipse (why not ou? It will automatically generate build.xml). In any case, you say that platform tools do you mean $ ANDROID_HOME / platform / android-9? Are you sure this is necessary for ant? I know that the ant build file itself is pretty empty, and most of the work is done in java.sh files, so to say that they are missing, it's cold, did you find an error in your new SDK?

0
source

I have other more serious problems with SDK2.3 (AVDs bust). I installed Ant builds OK to work with 2.2, and looked to see if Ant would build. My custom build.xml overloaded quite a bit of material in ant_rules_r3.xml, but still used it. I noticed that now it has been removed and replaced with main_rules.xml, which is slightly different. 'project.libraries' replaces 'android.libraries' for something. It's probably worth looking at the differences if your build.xml was based on ant_rules_3.

I will not look at it myself until my main problem is fixed.

0
source

More articles:


All Articles