jvm

We use sbt-dynver to set the version for the Play project based on git tags.
E.g. when you run sbt in the Play project folder you will see:

// If you haven't you need to get the Play framework source code
git clone git@github.com:playframework/playframework.git
cd ./playframework

// You are in the master branch now, from which we want to rele

Reference: https://issues.apache.org/jira/browse/INFRA-22697

Apparently testcontainers requires $HOME/.docker/config.json to be a valid JSON file.

touch ~/.docker/config.json
// lauch some test containers tests will now fail

echo '{}' > ~/.docker/config.json
// lauch some test containers tests will now succeeds

rm ~/.docker/config.json
// lauch some test containers tests will 

aside with FAIL_FAST.

Current, if we try to run a more recent Java class in an old JVM, we get the following error message:

Error: LinkageError occurred while loading main class some.Class
	java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=some/Class, offset=6

However, it is not so easily to detect that the class was compiled with a version above the supported by the JVM.Hotspot

Add how to configure code style in Contributing.
Adding an .editorconfig file will help to auto apply code style in some IDEs.