I know how to specify the release key store in the Android Maven assembly, but no luck doing the same with the debug assembly.
The methodology for creating the release can be found here - https://code.google.com/p/maven-android-plugin/wiki/SigningAPKWithMavenJarsigner .
When creating debug builds, the android-maven-plugin sign-> debug setting should be true and the release configuration should be false, but if debugging is set to true, the maven-jarsigner-plugin configuration seems to be ignored.
When using (android-maven-plugin):
<sign> <debug>true</debug> </sign>
And specifying the key (maven-jarsigner-plugin):
<goals> <goal>sign</goal> </goals> <phase>package</phase> <inherited>true</inherited> <configuration> <archiveDirectory></archiveDirectory> <includes> <include>${basedir}/someFolder/target/*.apk</include> </includes> <keystore>${basedir}/someFolder/debug.keystore</keystore> <storepass>android</storepass> <keypass>android</keypass> <alias>androiddebugkey</alias> </configuration>
The default line will use debug.keystore in my .android directory. If I delete / rename debug.keystore, it will just create a new one.
The reason I want to specify debug.keystore is because I am working on a team of several people and we use Google Maps v2. The only access token in the v2 Maps API instead of one team member is our desire.
thanks
EDIT:
My current workaround is a script package with my repo to replace their debug.keystore:
cp -r someFolder/debug.keystore ~/.android/debug.keystore
android maven android-maven-plugin
snotyak
source share