Android ant build: debug and release targets?

Up vote 4 down vote favorite 1 share g+ share fb share tw.

According to the 'help' target documentation: debug: builds the applications and signs it with a debug key release; builds the application: the generated APK file must be signed before it is published Here is what I found, which is a bit different than what I expected: debug: ignores keystore definitions in build. Properties whether you specify them or not. Which kesystore file is it using?

The same as Eclipse: the default debug. Keystore file in your Documents and Settings? It creates two files: -debug-unaligned.

Apk (signed, unaligned) -debug. Apk (signed, aligned) release: 'help' says it doesn't sign it. It creates these files: -unsigned.

Apk (unsigned, unaligned) The next two are only if you have the values specified in build. Properties: -unaligned. Apk (signed, unaligned) -release.

Apk (signed, aligned) Any helpful comments / verifications will be greatly appreciated. Android ant link|improve this question edited Jun 10 '11 at 23:01Lukas Knuth6,7043421 asked Jun 10 '11 at 21:11charlest1036 85% accept rate.

The same as Eclipse: the default debug. Keystore file in your Documents and Settings? Yes.

Thanks for the confirmation. – charlest Jun 12 '11 at 23:23 Thank you! I am assuming it's ok for my teammates to overwrite their default debug.

Keystore files with mine? Eclipse doesn't try to overwrite this file, right? – manisha Jul 12 '11 at 19:09 @manisha: I am not aware that Eclipse overwrites the file.

– CommonsWare Jul 12 '11 at 19:16 @CommonsWare - Sounds good. We tried it out and it seems to be working. My teammate can build from the command line using Ant and can also build from Eclipse.

This post helped us out a lot, thank you for your answer! – manisha Jul 14 '11 at 17:21.

As far as the release target goes, you will get behaviour like this: If you have lines like: key. Store=c:/users/me/my-release-key. Keystore key.

Alias=release_alias key.store. Password=myStorePassword key.alias. Password=myAliasPassword in your build.

Properties, it will automatically build and sign your apk with no prompting for anything. If you comment out the last two lines, then it will prompt you for the passwords, then complete a signed build if the passwords are OK. If you don't have any of the above lines, then it will just build you an unsigned apk with no prompting for anything and end with: -release-nosign: echo No key.

Store and key. Alias properties found in build.properties. Echo Please sign C:\dev\projects\AntBuilds\MyProject\bin\MyProject-unsigned.

Apk manually echo and run zipalign from the Android SDK tools.

That's what I thought: the 'release' part of help could use a little clarification probably, but you find it out the 1st time you do it. I like the prompting for passwords processing. – charlest Jun 12 '11 at 23:17 1 btw: thanks for the reply!

– charlest Jun 12 '11 at 23:18.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.