Can no longer create UrlFetchTransport since GAE SDK 1.6.6 #125
Labels
priority: p0
Highest priority. Critical issue. P0 implies highest priority.
🚨
This issue needs some love.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
From yan...@google.com on June 06, 2012 10:26:37
Version of google-http-java-client (e.g. 1.5.0-beta)? 1.9.0-beta Java environment (e.g. Java 6, Android 2.3, App Engine)? App Engine, starting with 1.6.6 SDK Describe the problem. Details here: http://stackoverflow.com/questions/10764671/verifyerror-after-upgrading-to-appengine-1-6-6-cannot-create-instance-of-urlfet but in summary UrlFetchTransport is unusable for local App Engine development How would you expect it to be fixed? I propose this simple fix: rename package com.google.api.client.extensions.appengine.http.urlfetch to com.google.api.client.extensions.appengine.http
This would avoid the classpath conflict, and anyway the "urlfetch" in the package name was unnecessary. We won't literally remove the com.google.api.client.extensions.appengine.http.urlfetch package, but rather deprecate it with a message to remove it in a future release.
Original issue: http://code.google.com/p/google-http-java-client/issues/detail?id=125
The text was updated successfully, but these errors were encountered: