gson support
readme: why & why not
Merge pull request #2 from togi/master

Gson support
cleanup
copy factory methods

* Add static copying factory methods to builder. The factory methods
  take either a builder or a value and copies all fields.

* Add a builder() method to values that can be used to copy the value
  into a new builder. The builder() method can be exposed by adding it
  to the value type definition.
readme: bump release version to 0.3
Merge pull request #3 from danielnorberg/copying

Copying
[maven-release-plugin] prepare release v0.3
[maven-release-plugin] prepare for next development iteration
readme: update todo
equals: handle other implementations
fail on class targets
print error messages when failing
Use List/Arrays hashCode algorithm

This is one more step towards the notion of an AutoMatter value type
working somewhat like a named tuple. This is also what guava/java 8+
Objects.hashCode uses.

Hopefully this makes it more likely that different implementations of
the type value interface can co-exist. Unfortunately AutoValue uses a
different algorithm and reserves the right to change it at any time.
Update README.md
tweak readme + example
Update README.md
remove @JsonProperty generation

* Do not clobber user provided @JsonProperty annotations.

* Eliminate processor dependency on jackson-annotations.
s/AutoMatterField/AutoMatter.Field/

Avoid autocomplete confusion when typing @AutoMa... and getting
offered both @AutoMatter and @AutoMatterField.
jackson: verify serialization configurability