rlalfo / google-http-java-client

Automatically exported from code.google.com/p/google-http-java-client
0 stars 0 forks source link

Improve the Android Gradle developer experience #203

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
External references, such as a standards document, or specification?

https://google-http-java-client.googlecode.com/hg/google-http-client-assembly/re
adme.html

http://developer.android.com/google/play-services/setup.html

Java environments (e.g. Java 6, Android 2.3, App Engine, or All)?

Android

Please describe the feature requested.

Our instructions for Android involve adding a bunch of jars and jar.properties 
files to the Android project libs folders and source jars to the libs-sources 
folder.  It is a bit of a pain to set up, and I am hearing complaints from 
developers about this.  For our sister projects oauth & api the problem is even 
worse as the number of jars grows.  

The current best practice for publishing Android libraries is the process that 
the Google Play services library uses.  See the setup directions link above.  
We should follow that model.

We might even go so far as to provide a download zip file customized for 
Android, calling it for example something like google-http-client-android.zip 
that contains 5 library projects: google-http-client_lib, 
google-http-client-protobuf_lib, google-http-client-gson_lib, 
google-http-client-jackson_lib, and google-http-client-jackson2_lib.

We should use a similar approach for the sister projects oauth & api.

Original issue reported on code.google.com by yan...@google.com on 8 Mar 2013 at 2:51

GoogleCodeExporter commented 9 years ago

Original comment by yan...@google.com on 28 Mar 2013 at 12:47

GoogleCodeExporter commented 9 years ago

Original comment by yan...@google.com on 29 Mar 2013 at 1:17

GoogleCodeExporter commented 9 years ago

Original comment by yan...@google.com on 10 Jun 2013 at 1:07

GoogleCodeExporter commented 9 years ago
Given the new Android build system and Android Studio announced at Google I/O, 
we're going to be focusing on that instead.

According to the documentation, we should be publishing 
google-http-client-android using AAR format instead of JAR.  That includes in 
particular the AndroidManifest.xml and proguard.txt.

We should also update our own two Android samples to Android Studio and Gradle.

References:
http://tools.android.com/tech-docs/new-build-system
http://tools.android.com/tech-docs/new-build-system/aar-format
http://developer.android.com/sdk/installing/studio.html
http://samples.google-api-java-client.googlecode.com/hg/tasks-android-sample/ins
tructions.html
http://samples.google-api-java-client.googlecode.com/hg/calendar-android-sample/
instructions.html

Original comment by yan...@google.com on 17 Aug 2013 at 12:11

GoogleCodeExporter commented 9 years ago

Original comment by ngmic...@google.com on 3 Sep 2013 at 8:01

GoogleCodeExporter commented 9 years ago
Android samples being updated here:
https://codereview.appspot.com/13654043/

Leaving this issue open for switching to AAR format for 
google-http-client-android.

Original comment by yan...@google.com on 11 Sep 2013 at 5:59

GoogleCodeExporter commented 9 years ago

Original comment by yan...@google.com on 27 Sep 2013 at 11:56