However, interesting possibilities exist about serialization: http://immutables.github.io/json.html#toc7 (also the rest of the JSON guide is a fun read).
Also they have this https://github.com/immutables/immutables/issues/44 ________________________________________ From: Zack Shoylev [zack.shoy...@rackspace.com] Sent: Monday, November 17, 2014 8:20 AM To: dev@jclouds.apache.org Subject: RE: Immutables.value I am guessing the maven-compiler-plugin can be configured to use the source/target we want. I am a little bit less sure about the guava aspect of it - especially because the generated code contains MoreObjects :) ________________________________________ From: Andrew Phillips [aphill...@qrmedia.com] Sent: Monday, November 17, 2014 8:02 AM To: dev@jclouds.apache.org Subject: Re: Immutables.value > Some work might have to be done (with the jclouds gson) to make sure > this works consistently with custom name serialization and to make > sure everything is consistent with autovalue. AutoValue classes will > still be used to parse json as returned by the service. > Thoughts? In general, I think anything that cuts down on boilerplate that we need to maintain without introducing overhead for our users is worth investigating to me. Could you put together a "straw man PR" so we can see what a piece of jclouds code would look like if we started using this? I'm curious how this will need to be set up from a CI point of you so that we can build (with Guava 18 and Java 7, if I understand correctly) but still release for Java 6 and older versions of Guava. Thanks for suggesting this, Zack! ap
