-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support apk / apklib artefacts #22
Comments
Hi, |
Hi @Vorta1, |
@Zlika I will see what I can do 👍 |
So I've had a go at making a simple Android project in maven: https://github.com/Vorta1/simple-android-app-build However despite my best efforts I can't come up with a way to avoid the build machine having to have the required platform of the Android SDK available for it to work... I believe the quickest way is to go to https://developer.android.com/studio/, scroll down to 'Command line tools only', download for your OS, run the sdk manager and download a platform of your choice, I chose platform level 25. Update this project's pom file for the android-maven-plugin configuration section and set the 'platform' level you chose to download and the 'path' to where the sdk is installed on your build machine. |
Hello,
bit of a long shot, but would it be possible for your plugin to do the same strip-jar process it does for jar artefacts for andrioid apk & apklib build artefacts?
We build these using the com.simpligility.maven.plugins.android-maven-plugin, which generates a META-INF folder and adds in a copy of an AndroidMainifest.xml file during the build which are date-time stamped with the machine time of the build, which means the md5sum of the resulting artefact (apklib/apk) isn't reproducible.
Is this something your plugin could help with?
Kind regards
Pete.
The text was updated successfully, but these errors were encountered: