The current docker-compose.yml is still in version 1, which is
deprecated: https://docs.docker.com/compose/compose-file/compose-versioning/
So if you try to run `docker-compose up` with a recent version of
docker-compose, the following error occurs:
(root) Additional property mysql is not allowed
Version 2.2 was chosen because it's not deprecated, but it also has been
released some time ago: Compose version 2.2 requires docker engine
version 1.13.0, which was released on 2017-01-18. So, with this version,
hopefully no users will have any issues either with deprecation warnings
or with a version that is not yet supported by their docker-engine.
As part of a process to build a BOSH release, I encountered the error
below while running `./mvnw package`:
```
[ERROR] Failed to execute goal pl.project13.maven:git-commit-id-plugin:3.0.1:revision (default) on project spring-petclinic: Could not complete Mojo execution...: Error: Could not get HEAD Ref, are you sure you have set the dotGitDirectory property of this plugin to a valid path? -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
```
That's because we are just interested on the source files for the BOSH
release, we don't care about repo metadata (so we exclude them).
Going through the [git-commit-id-maven-plugin
docs](https://github.com/git-commit-id/git-commit-id-maven-plugin/blob/master/maven/docs/using-the-plugin.md)
we learned it is possible to prevent the failure above via
configuration.
We propose then to set
`<failOnUnableToExtractRepoInfo>false</failOnUnableToExtractRepoInfo>`,
enabling use cases similar to ours.
FWIW `failOnNoGitDirectory` is already set to false.
