You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Anyway, a simple fix might be to just split off the gson and jackson support into separate google-http-client-gson & google-http-client-jackson jars. Down side: two mores projects to manage (but that should be easy enough to manage). We should then list it in the readme.html with a qualifier for when it may be needed, e.g.:
google-http-client-gson (only if using GSON library)
gson
google-http-client-jackson (only if using Jackson library)
From yan...@google.com on May 05, 2012 07:56:34
External references, such as a standards document, or specification? http://google-http-java-client.googlecode.com/hg/google-http-client-assembly/readme.html http://javadoc.google-http-java-client.googlecode.com/hg/1.8.3-beta/com/google/api/client/json/gson/package-summary.html http://javadoc.google-http-java-client.googlecode.com/hg/1.8.3-beta/com/google/api/client/json/jackson/package-summary.html Java environments (e.g. Java 6, Android 2.3, App Engine, or All)? All Please describe the feature requested. The readme.html says that gson and jackson jars are dependencies. But that's really only true if you are using GSON or Jackson as the low-level JSON library. In particular, for applications based on Android Honeycomb (SDK 3.0) or higher that are using Android's native JSON library, or for applications that aren't using JSON (admitted rare these days), this dependency should be unnecessary. The problem is for Android it is highly recommended to use ProGuard, and it expects all dependent jars to be on the classpath. This is just an inconvenience. The good news is that it shouldn't actually cause the compiled application to be any larger, because in theory ProGuard should just strip out the jar.
Anyway, a simple fix might be to just split off the gson and jackson support into separate google-http-client-gson & google-http-client-jackson jars. Down side: two mores projects to manage (but that should be easy enough to manage). We should then list it in the readme.html with a qualifier for when it may be needed, e.g.:
Original issue: http://code.google.com/p/google-http-java-client/issues/detail?id=103
The text was updated successfully, but these errors were encountered: