@{elseText}@{elseText}Running tests ...Uninstalling @{app.package} from the default emulator or device...Project Name: ${ant.project.name}Switching between debug and non debug build: Deleting previous compilation output...Switching from instrumented to non-instrumented build: Deleting previous compilation output...Resolving Build Target for ${ant.project.name}...----------Creating output directories if needed...----------Resolving Dependencies for ${ant.project.name}...----------Building Libraries with '${project.libraries.target}'...----------Building tested project at ${tested.project.absolute.dir} with '${tested.project.target}'...Handling aidl files...----------Handling RenderScript files...----------Handling Resources...----------Handling BuildConfig class...
Instrumenting classes from ${out.absolute.dir}/classes...
-include "${proguard.configcmd}"
-include "${out.absolute.dir}/proguard.txt"
-injars ${project.all.classes.value}
-outjars "${obfuscated.jar.file}"
-libraryjars ${project.target.classpath.value}
-dump "${obfuscate.absolute.dir}/dump.txt"
-printseeds "${obfuscate.absolute.dir}/seeds.txt"
-printusage "${obfuscate.absolute.dir}/usage.txt"
-printmapping "${obfuscate.absolute.dir}/mapping.txt"
Signing final apk...Release Package: ${out.final.file}No key.store and key.alias properties found in build.properties.Please sign ${out.packaged.file} manuallyand run zipalign from the Android SDK tools.proguard.config is ${proguard.config}Proguard.config is enabled***************************************************** Android Manifest has debuggable=true ******** Doing DEBUG packaging with RELEASE keys *****************************************************Signing final apk...Release Package: ${out.final.file}Instrumented Package: ${out.final.file}Running tests...Settting permission to download the coverage file...Downloading coverage file into project directory...Extracting coverage report...Cleaning up temporary files...Saving the coverage reports in ${out.absolute.dir}Installing ${out.final.file} onto default emulator or device...Install file not specified.'ant install' now requires the build target to be specified as well. ant debug install ant release install ant instrument installThis will build the given package and install it.Alternatively, you can use ant installd ant installr ant installi ant installtto only install an existing package (this will not rebuild the package.)Android Ant Build. Available targets: help: Displays this help. clean: Removes output files created by other targets. The 'all' target can be used to clean dependencies (tested projects and libraries)at the same time using: 'ant all clean' debug: Builds the application and signs it with a debug key. The 'nodeps' target can be used to only build the current project and ignore the libraries using: 'ant nodeps debug' release: Builds the application. The generated apk file must be signed before it is published. The 'nodeps' target can be used to only build the current project and ignore the libraries using: 'ant nodeps release' instrument:Builds an instrumented package and signs it with a debug key. test: Runs the tests. Project must be a test project and must have been built. Typical usage would be: ant [emma] debug install test emma: Transiently enables code coverage for subsequent targets. install: Installs the newly build package. Must either be used in conjunction with a build target (debug/release/ instrument) or with the proper suffix indicating which package to install (see below). If the application was previously installed, the application is reinstalled if the signature matches. installd: Installs (only) the debug package. installr: Installs (only) the release package. installi: Installs (only) the instrumented package. installt: Installs (only) the test and tested packages (unless nodeps is used as well. uninstall: Uninstalls the application from a running emulator or device. Also uninstall tested package if applicable unless 'nodeps' is used as well.