In 5b6f1e9, we added the ability to customize the FieldNamingStrategy, so that you can control the serialized names on auto-value types. I've added code to propagate the same names used for deserialization to also be used for serialization. With this in, customizing FieldNamingStrategy is no longer needed, and should be removed. You can merge this Pull Request by running:
git pull https://github.com/adriancole/jclouds adrian.serialized-names-input Or you can view, comment on it, or merge it online at: https://github.com/jclouds/jclouds/pull/596 -- Commit Summary -- * JCLOUDS-750 Revert 5b6f1e929ef4b6438facc06df0f081ddef8c9cf6 in favor of tighter contract on @SerializedNames. -- File Changes -- M core/src/main/java/org/jclouds/json/SerializedNames.java (27) M core/src/main/java/org/jclouds/json/config/GsonModule.java (15) M core/src/main/java/org/jclouds/json/internal/NamingStrategies.java (34) M core/src/main/java/org/jclouds/reflect/Reflection2.java (2) M core/src/test/java/org/jclouds/json/JsonTest.java (93) M core/src/test/java/org/jclouds/json/internal/DeserializationConstructorAndReflectiveTypeAdapterFactoryTest.java (3) M core/src/test/java/org/jclouds/json/internal/NamingStrategiesTest.java (11) -- Patch Links -- https://github.com/jclouds/jclouds/pull/596.patch https://github.com/jclouds/jclouds/pull/596.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/596
