Skip to content
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

build an AAR and .pom file for Maven repos #197

wants to merge 2 commits into from


Copy link

commented Sep 18, 2015

AAR libraries are the standard for Android these days when making libraries that include anything in addition to Java classes. This adds AAR and .pom generation to the standard build system. The .pom file is needed for Maven repos like MavenCentral and jCenter, which are the default library repos for gradle for Android.

The products of this can then just be uploaded to jCenter/MavenCentral with GPG .asc signatures on both the .aar and .pom files. I can handle the uploading to jCenter if you're OK with it being managed under the Guardian Project group.

eighthave added some commits Oct 14, 2014

do not put timestamps in javadoc-generated files
This aids reproducible builds: besides the timestamp, `javadoc` will create
the exact same files across different machines, java versions, etc.
build AAR library and .pom file for Maven repos
AAR is the standard Android library format for distributing a library that
has more than just Java classes.  A .pom file is needed to put that .aar in
a Maven repo like MavenCentral or jCenter.

This comment has been minimized.

Copy link

commented Sep 21, 2015

Hello Hans-Christoph,

Thanks for the pull request. As you've seen over on the SQLCipher discussion site, this has been on our radar for some time. Mark Murphy also published some packaging resources in sqlcipher-artifict. We've been working hard on a few other high priority issues, e.g. the compatibility issues on API 23 and as a result, haven't had time yet to finish testing and commit our own changes for this. That said, we are planning to address the new requirements very soon (likely within the next week), since this is a priority for the community.

With regard to distribution of the AAR packages, we are planning to take on distribution responsibility as a part of our ongoing SQLCipher release processes. This will ensure both that updates are in lock-step with the standard release process, and that the archives are signed using the same Zetetic keys used on all of the other SQLCipher platform packages for consistency.

We'll let you know as soon as the relevent updates are in place. Thanks!


This comment has been minimized.

Copy link
Collaborator Author

commented Sep 21, 2015

If you're willing to manage the whole thing, that works even better for me :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.