JDBC runtime tests break all branch builds.

Some tests in jdbc-runtime require the jdbc-runtime-0.x.0.jar to be present in the maven repository before they can succeed.

This causes builds to break on "clean" branches the first time they are built (since the module is not installed until after the tests succeed).

This causes wrong behaviour on "non-clean" branches like master since the tests are run against the "old" jdbc-runtime.jar present in nexus instead of the module currently under test.

Some possible solutions have been discussed:

• Add a maven-invoker-plugin to create another nexus for integration testing within the module,
• Move these runtime tests to a separate module that should be executed afterwards ('jdbc-integration-test` to be run after `jdbc-runtime`),
• Add a "warm-up" step to branch builds that run mvn clean install -DskipTests -DskipITs before running the actual build, thus ensuring that the current branch's modules are already present in the branch maven before the tests are run.