v0.7.0

• Clean up the container afterwards #27; when the @PreDestroy hook is called, the container is force removed (docker rm -fv ${containerName}). Not called when force-clean-afterwards == false.
• Clean up log files afterwards #25 and #22; when the @PreDestroy hook is called, the Docker std out/err files are removed.
• Remove port blockers #24 and #20; when a docker container is detected that occupies the port that is about to be used to launch the new container, the occupying container is stopped (docker stop ${occupyingContainerName}). Not called when stop-port-occupying-container == false. If this feature is disabled, the library will generate a warning when a port-blocker is detected.
• Detected terminated containers #26; the library not only detects running containers (docker ps), but also the others, such as terminated ones (docker ps --all). Terminated containers would not be removed, but still blocked the launch of a new container with a similar name. In the subsequent step, terminated containers with a similar name are now also removed.
• Auto-complete on kebab case; in your IDE, entering the properties in your yml is now supported on kebab casing (ie, force-clean, instead of forceClean), see 42BV/spring-boot-starter-docker#3

v0.6.0

• #16 - If no port is set, read the port from spring.datasource.url. If not supplied, set to default 5432.
• #14 - use the startup verification text that ascertains Postgres is ready for taking connections

v0.5.0

• #10 - docker image ls did not work for Docker v1.12 (highest Docker version at Linux atm), so changed to docker images
• #12 - existing containers with the target container name are now removed, including the attached volumes
• #13 - containers are checked to exist by matching image name, image version and container name. It should check just on the container name. Does now.

v0.4.0

• #8 - introduced a delay after startup verification. Postgres is not really ready, so the dev can add an extra sleep in ms
• #9 - log the error file at level ERROR when the CLI process exits with an error code other than 0