Add docs for AutoFactory#className.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=65461246
Restore development version number
Fix a bug where @AutoValue generates broken code when a property of an AutoValue object has a type which is ambiguous thanks to a type defined in the @AutoValue annotated class. E.g:

final class EnclosingClass extends BaseClass {

static class BaseClass {
static class Optional {}
}

@AutoValue
abstract static class ChildClass extends BaseClass {
public abstract com.google.common.base.Optional getOptional();
//...
}
}

The above code will generate a constructor for AutoValue_EnclosingClass_ChildClass which expects an instance of BaseClass.Optional.

This fix resolves this issue by adding all non-private types which are declared by the @AutoValue annotated type, any of its supertypes, or any of the interfaces it implements, to the list of ambiguous types in TypeSimplifier.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=67047217
In AutoValueProcessor, replace the funky custom template language for code generation with Apache Velocity.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=67049155
Update the pom.xml for AutoValue to reflect the change to use Apache Velocity. Also remove the jsr305 dependency, since the processor now recognizes @Nullable annotations regardless of package.

This CL is diffbased against the CL to introduce Velocity, which is itself diffbased against the CL to fix the manual auto_moe_test.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=67050350
If an exception occurs during @AutoValue processing, always include its stack trace in the resultant compiler error message, rather than only if debugging.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=67064823
In the AutoValue processor, set the context class loader to a known value before initializing Velocity, so it doesn't go loading auxiliary classes from another copy of itself.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=67529348
Move most of the tests from AutoValue's CompilationErrorsTest into a new CompilationTest that uses compile-testing. The tests that remain test warning generation, which is planned but not yet implemented in compile-testing.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=68275826
Add support for @GwtCompatible(serializable = true) to AutoValue.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=68285700
Fix %x oversight pointed out by nfm@.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=68378221
Add @SuppressWarning("unused") to the deserialize method's parameters and the dummy field.

Any chance of adding the @SuppressWarning("unchecked") to instantiate(..) only when it is needed? Our project has a zero warning policy on our Eclipse project and having this unused @SuppressWarning kind of annoying... :(
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=68380630
Add a test to AutoValue's CompilationTest that uses compile-testing's generatesSources clause to check that the generated code is what we expect it to be.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=68848125
Copy MoreTypes from dagger to auto-common so that it can be used by auto-value. Eventually it should be moved rather than copied.

Also refactor the AutoValueProcessor in ultimate preparation for future variations.

-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=69423031
MOE_MIGRATED_REVID=69154604
Add common to the convenience pom, and bump version numbers on value