-
The
com.avast.gradle.docker-compose
plugin is no longer automatically applied. You have to apply theeu.xenit.docker-compose
plugin when you needcomposeUp
andcomposeDown
tasks.Old New plugins { id "eu.xenit.docker-alfresco" version "4.1.2" }
plugins { id "eu.xenit.docker-alfresco" version "5.0.0" id "eu.xenit.docker-compose" version "5.0.0" }
apply plugin: "eu.xenit.docker-alfresco"
apply plugin: "eu.xenit.docker-alfresco" apply plugin: "eu.xenit.docker-compose"
plugins { id "eu.xenit.docker" version "4.1.2" }
plugins { id "eu.xenit.docker" version "5.0.0" id "eu.xenit.docker-compose" version "5.0.0" }
apply plugin: "eu.xenit.docker"
apply plugin: "eu.xenit.docker" apply plugin: "eu.xenit.docker-compose"
-
Configuration and tasks now use Gradle
Property<>
. This usually does not affect yourbuild.gradle
, but if you explicitly call getters instead of accessing as a property, keep in mind that the return type has changed. BecauseProperty<>
is now used, setters have been removed. Instead of usingsetFoo(bla)
, you should now usegetFoo().set(bla)
. -
Automatic tagging has been disabled by default. You can re-enable automatic tagging based on branch name and build number by using:
dockerAlfresco { dockerBuild { automaticTags = true } }
-
resolveAlfrescoWar
andresolveShareWar
tasks have been renamed tostripAlfrescoWar
andstripShareWar
. -
gradle-docker-plugin
has been upgraded from 4.6.2 to 6.1.1. This should not affect basic usage, but may break more advanced usecases. See the breaking changes in the changelog there. -
The
pushTag*
tasks that allow to push individual tags have been removed. UsepushDockerImage
to push all tags of the docker image. -
Gradle task classes have been moved out of the
eu.xenit.gradle.tasks
packageDockerfileWithCopyTask
has moved toeu.xenit.gradle.docker.tasks.DockerfileWithCopyTask
- Other tasks have been moved to the
eu.xenit.gradle.docker.alfresco.tasks
package