Issue #103 Do not use Multi-Modules

[bytefish]

I have merged all modules into a single jar, so we don't build multiple-modules anymore. In Issue #103 it became clear, that targetting multiple JDKs using a classifier is apparently not possible. The project doesn't use any specific Java11 Features, so we should be safe to build for 1.8 only.

[jonfreedman]

Note we're still actually building in github actions using JDK 11

[bytefish]

While I know using ErrorProne and NullAway catches some errors, it leads to build errors, like this:

Error:java: java.lang.RuntimeException: java.lang.NoSuchMethodError: com.sun.tools.javac.util.JavacMessages.add(Lcom/sun/tools/javac/util/JavacMessages$ResourceBundleHelper;)V
Error:java: Caused by: java.lang.NoSuchMethodError: com.sun.tools.javac.util.JavacMessages.add(Lcom/sun/tools/javac/util/JavacMessages$ResourceBundleHelper;)V
Error:java: at com.google.errorprone.BaseErrorProneJavaCompiler.setupMessageBundle(BaseErrorProneJavaCompiler.java:202)
Error:java: at com.google.errorprone.ErrorProneJavacPlugin.init(ErrorProneJavacPlugin.java:40)

I know there are special ways to set it up for Java 1.8:

• https://github.com/uber/NullAway/wiki/Configuration#maven

We can activate it lateron again, for now I would like to have the build compiled again.

[qlty-cloud-legacy]

Code Climate has analyzed commit 20b695a and detected 34 issues on this pull request.

Here's the issue category breakdown:

Category	Count
Complexity	8
Duplication	26

View more on Code Climate.