Ah. so it actually only propagates the method annotations. This works
for jackson, but not gson, as gson @SerializedName is on fields. Now
remember that if your api is consistent, all you need to do is
configure the global gson to use snake case. that avoids this issue
completely.

ex. 
gsonBuilder.setFieldNamingPolicy(FieldNamingPolicy.LOWER_CASE_WITH_UNDERSCORES)

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/100#issuecomment-60499150

Reply via email to