WSL detection

localhost used as containers host if WSL detected #294

Gradle Plugin Portal publishing fix

The previous version wasn't published to Gradle Plugin Portal.

V2 suffixes handled

Docker Compose V2 changed the format of suffixed of scaled instances - it uses - instead of _. This change is reflected now in environment variables and system properties handling.

#332

Regular properties instead of raw Groovy properties

The plugin internals refactored in order to use regular Gradle properties (Property<String> etc.) instead of raw Groovy properties that are supposed to be legacy for a long time.

It is also a prerequisite to make #307 happen (Gradle Configuration Cache support).

EDIT: It was not intentional but this release could contain a breaking change for some users. As we use DirectoryProperty and RegularFileProperty instead of custom getters/setters, following properties cannot be set from a String, and java.io.File is required instead. So e.g. project.file('relativePath') must be used instead of plain 'relativePath':

• captureContainersOutputToFiles
• containerLogToDir
• dockerComposeWorkingDirectory
• captureContainersOutputToFile
• composeLogToFile

Also, Kotlin users could be affected, e.g. as described in #315

Also, removeImages cannot be specified using a String but an exact value must be used, e.g. com.avast.gradle.dockercompose.RemoveImages.All.

Plugin reverted to Gradle 6.x

The upgrade to Gradle 7.x includes update of Groovy from 2.5 to 3, and this change is not forward compatible. So we are reverting this plugin to Gradle 6.9 to support also older Gradle versions. Support in Gradle 7.x is not affected as the new Groovy version is backward compatible.

Minor improvement to support Gradle 7.0.2

Gradle 7.0.2 doesn't automatically inject Project, so it is made manually in the plugin, to support also this version.

Minor fixes and improvements

Mainly fixes an issue when looking for a default list of services but fixes more code-paths that rely on version parsing.

This release also contains an internal change - the objects are not created using the constructor but via ObjectFactory, and take advantage of standard Gradle services injection.

ComposeSettings compiled statically

This is a blind attempt to fix #305 (an issue caused by migration to Gradle 7.x that uses a new major version of Groovy).

retainContainersOnStartupFailure introduced

0.14.4

fix: retainContainersOnStartupFailure copied

nested method introduced

The new nested method allows getting previously defined nested settings. This solves #289 so Kotlin users are able to access servicesInfo of a nested settings.