Fix #151; Java 7 -> 8 compatibility.
Fix many javadoc errors and warnings
Updated plugin versions referenced in pom.xml
Merge pull request #154 from sharwell/updates-for-release

Updates for release
[maven-release-plugin] prepare release 3.5.2
[maven-release-plugin] prepare for next development iteration
Merge pull request #155 from sharwell/release/3.5.2

Release/3.5.2
Update CHANGES.txt
When you name your source files *.c, MSVC (2010) assumes it's compiling C, which means C89. All block-local variables need to be declared at the beginning of your functions.
Or at begginning of {} block.
Fix memory leak when using lexer rule label references.

Inspired by bennyk. Since this patch uses std::unique_ptr the build now requires
a compiler supporting at least some of C++11 features.
Fix lexer labels onto EOF token

+ minor fix - remover StringTemplate warning in matchSet/terminalOptions
All Token labels are declared as const*
Fix to lexer label refs(array form)

+= operator
Add test for lexer rule labels

Python target used as an example
lexer token names
fix for filtering option
fuzzy lexer test
use gnu make wildcards instead of shell ones
remove executable flag from header files
Do not use EOF macro in generated code

= The current code depends on the fact that EOF is #define EOF -1 is some standart C headers
= While generated enums use EOF_TOKEN
= Moreover EOF(-1) is signed value while LA an other methods return ANTLR_UINT32, this cause plenty of compiler warnings
= Moreover clang++11 refuses compile code like this:

    switch(this->LA(1)
    {
    case EOF: // -1
    ...

This patch sets EOF_TOKEN = std::numerical_limits<ANTLR_UINT32>::max()
All generated local varibles are of type ANTLR_UINT32 (instead of int)
Generated conditions use EOF_TOKEN instead if pure EOF