Fixes for Javadoc Warnings
Merge branch 'release/0.1.1' into develop
Preparing for next development cycle.

Srsly guys, rly need to automate this.
Merge branch 'develop' into feature/javadoc
Updated README.md to reflect current branch in Travis CI badge.

There has to be a better way to do this...
Explicitly added maven-clean-plugin.

Leaving out configuration element, as I have not gotten it quite how I want it.
Ignore diff files, created by SourceTree for patch(s).
Added Maven profile for eclipse.

Explicitly cleaning bin/
Merge branch 'feature/maven-clean-plugin' into develop
Added reporting element to pom
Fixed typos.
Added blank lines for readability.
Merge branch 'feature/pom-quickfix' into develop
Added some more check style rules and fixes.
Added checkstyle cacheFile property.
Added checks for Javadoc comments.
Merge commit '6cca9c67439a3ea6ea771b4d0839145c98c0459d' into feature/javadoc

This also means tag:pre-checkstyle-checker.xml-template of branch: feature/checkstyle-duex
The check style additions brought in will break the build when running mvn test, read Travis CI. This is the point. The build should only pass when all Javadoc checks pass. This makes for more maintainable and readable code. I am one for self documenting code, however Javadoc integration in IDEs is fucking fantastic and if this library is ever used as a 3rd party module, having the Javadocs available is invaluable.
Java 8 is pretty fucking dope.
Added more check style configuration and documentation. Removed unnecessary element.
Added pmd plugin to build and report.