Jan Burkhardt

The code of `ConsumingQueueIterator` is not thread safe because it is not using an atomic operation in `computeNext` we have this stacktrace once in our whole cluster ``` java.util.NoSuchElementException: null...

https://avro.apache.org/ for example creates classes which implement `Comparable` but not `Comparable`. Instead every avro class extends `SpecificRecordBase` which also contains the implementation of `compareTo`. Because of this its not easy...

I am creating a library (jar) to be consumed by different java applications. Both need to be able to serialize. So I do need the `com.google.flatbuffers:flatbuffers-java` dependency in both projects...

in debian package branch, yada is necessary for building dist target. dist target is platform independet, but yada is debian specific

when jdbc session times out, you're unable to close henplus with ctr + c or with a normal kill, only kill -9 works.

for some unknown reasons the test are failing when upgrading the gradle wrapper (tested 4.1 and 4.4) execute `./gradlew wrapper --gradle-version 4.4` twice

atm this is just a TODO

SpotBugs, the successor of Findbugs is released: https://github.com/spotbugs/spotbugs - use SpotBugs in test - review/update SpotBugs annotations, especially non JSR305 annotations

it is possible to declare your own JSR305 annotation like described in https://stackoverflow.com/questions/7658353/is-parametersarenonnullbydefault-applies-to-method-return-values-too/13429092#13429092

find a way to honor annotations at package-info.java