WIP! Use MOJO logging instead of sysout and some docs

[astubbs]

Attempts to address #8

Implementation as is prints out DEBUG level also, and doesn't appear to routing through the proper logging system as the actual output appears differently to other maven logging statements -

[INFO] Changes detected - recompiling the module!
[INFO] Compiling 26 source files to /Users/antony/repos/confluent/async-consumer/async-consumer-core/target/test-classes
[info] Jabel static initialising ByteBuddy
[info] Jabel ByteBuddy initialisation complete
[debug] Jabel: initialized. Enabled features:
	- LOCAL_VARIABLE_TYPE_INFERENCE
	- DIAMOND_WITH_ANONYMOUS_CLASS_CREATION
	- SWITCH_RULE
	- EFFECTIVELY_FINAL_VARIABLES_IN_TRY_WITH_RESOURCES
	- PRIVATE_SAFE_VARARGS
	- VAR_SYNTAX_IMPLICIT_LAMBDAS
	- TEXT_BLOCKS
	- SWITCH_EXPRESSION
	- SWITCH_MULTIPLE_CASE_LABELS

[INFO] ...

Implementation info from: https://stackoverflow.com/a/22423213/105741

Tried using Slf4j also, and got an unimplemented slf4j subsystem response, so doesn't seem like that's being used...

[bsideup]

Hi @astubbs,

the Java Compiler has its own logging system that one should be used. Sorry for not having time to fix #8 yet, but maybe you would like to explore it more?

[astubbs]

Ah! Thanks, I'll check it out..

[astubbs]

@bsideup you're not referring to java.util.logging.Logger, are you?