release 1.5.0

• A fix in the fluent generator. In prior versions when a grammar started with an optional method or with an optional
  expression (e.g.: zero or more times alternative methods, anything that is (...)* in the syntax description) then
  the generated interface structure required ONE or more invocations instead of ZERO or more.

• Fluent generator was annotated with @AnnotationBuilder and hence, there is a @Fluent annotation in
  core-annorations.

• Jdocify was developed.

• GeciException thrown from the generators are caught, enriched with the source file information the generator was
  working on and then thrown again in the Geci process. This eliminates the need to fetch the file name from the source
  code and to add it to the exception where it is originally thrown.

• Lexical analyser keeps the original format of the characters and strings
  and it can also be queried in case the generator needs to know the exact
  escape sequences in the string or character literal.

• Generators replying on the lexical analysis do not need to delete a
  lexical element from the list of lexical elements of a source file and
  insert a new one when it can simply be done replacing the lexeme string.
  It is not possible to change the type of the lexical element though.

• A bug prevented the proper comparing of any Java file that contained
  string or character with \n or \r literals.
  The code was throwing an exception thus code generation was aborted.

• A bug prevented the proper comparing of any Java file that contained
  hexadecimal long literals. The code was throwing an exception thus
  code generation was aborted.