4.3.0

This minor release addresses the following issues:

• #589 Can now run on Gradle 7 (tested up to version 7.1.1)
• #594 Can now deploy to a replica cluster via mlDeployToReplica
• #596 Updated description of mlDeployTasks
• #599 Improved error message when mlUnitTest is not able to write results to a directory
• And includes improvements in ml-app-deployer 4.3.0, which includes now depending on ML Java Client 5.5.0

4.2.1

This bugfix release addresses the following items:

• #592 All mlDeploy/mlUndeploy tasks now depend on mlPrepareBundles
• And a couple fixes in the ml-app-deployer 4.2.1 release that pertain to forest creation for a database that should only have forests on one host

4.2.0

This release is the first to be published at Maven Central - https://search.maven.org/artifact/com.marklogic/ml-gradle

Most of the changes in this release can be found in the ml-app-deployer 4.2.0 release notes and the ml-javaclient-util 4.2.0 release notes, which includes upgrading the MarkLogic Java Client version to 5.4.0.

The few changes to ml-gradle itself consist of:

• Updates to example projects - #462, #545, #578, and #590
• This project now uses version 6.9 of the Gradle wrapper; the 3 JavaExec tasks - CorbTask, MlcpTask, and ShellTask - now use "mainClass.set" instead of "setMain", the former being the preferred approach in Gradle and now required by 6.x

4.1.1

This bugfix release just bumps up a couple dependencies, primarily so that it now depends on ML Java Client 5.3.2:

• ml-app-deployer 4.1.1
• marklogic-data-movement-components 2.2.1

4.1.0

This release upgrades all of its dependencies to the latest versions and runs on Java 8, matching its dependency on MarkLogic Java Client 5.3.0, which runs on Java 8 as well.

Highlights of other issues addressed by this release:

• #567 MlcpTask no longer prints a password when running a COPY operation
• #570 A regression in mlPreviewDeploy was fixed
• #571 A regression in mlLoadDefaultPipelines was fixed
• #574 mlUpdateIndexes ensures forest creation is always disabled when it runs
• Includes issues addressed by ml-app-deployer 4.1.0

4.0.4

This bugfix release addresses the following items:

• #554 MlcpTask and CorbTask stopped working due to a change in Gradle 6.4; they now work again (this change in Gradle 6.4 affected a number of Gradle plugins)
• #558 CallResourceTask no longer eagerly (and needlessly) instantiates a DatabaseClient
• And one change in ml-app-deployer 4.0.3 - query rolesets are no longer updated, as the Manage API does not support that

4.0.3

This bugfix release addresses the following items:

• #544 DMSDK tasks now work when running on Java 9 or higher. This was a regression in 4.0.0, as the marklogic-data-movement-components dependency was still depending on ML Java Client 4.x instead of 5.x. ml-gradle now depends on version 2.0.0 of this library, which depends on ML Java Client 5.1.0.
• Includes a couple fixes in ml-app-deployer 4.0.2

4.0.2

This bugfix release includes the following items:

• #552 mlExportResources was not working properly for exporting CPF resources
• Fixes from ml-app-deployer 4.0.1

3.17.1

This bugfix release addresses a single issue:

• #552 mlExportResources was not working properly for exporting CPF resources

4.0.1

This bugfix release fixes an issue in 4.0.0:

• #536 mlExportResources now works again, and it will use the last path specified in mlConfigPaths (in a DHF application, this will be src/main/ml-config by default, and not src/main/hub-internal-config).