[#13] support for mapper with a constructor of one java.lang.XXX parameter
[#13] use "this." to avoid collision between params and properties

in Mapper method, explicitly use "this." qualifier to call properties to avoid collision with the name of a parameter of the mapper method
also add interface Iterable to FluentIterable to make direct use of the internal Iterable possible without actually creating a List of a Set
[#13] support Mapper in constructor by differing generation of files

when a dedicated class annotated with @Mapper has at least one type with the ERROR TypeKind, parsing won't failed but will be differed to the end of the round or to all the next round (except the last one)
also all type successfully process and generated are logged so that during differed processing of classes with resolution errors, these resolution errors could be found fixed
if all resolution errors are found fixed, a new parsing of the class annotated with @Mapper is triggered which will now how to fix resolutions reported as errors by Javac

unfortunatly, the algorithm implemented here has drawbacks:
 - can not yet support references to a Mapper which is not in the same package as the class annotated with @Mapper
 - the resolutions are infered based on naming convention (so the solution can hardly evolve to new generated files)
 - we can not yet know which of two classes with the same simpleName is actually referenced by the class annotated with @Mapper
 - if unresolved maper in the class annotated with @Mapper has type arguments or upper/lower bound, they are currently lost