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).

4.0.0

This is a major release due to its dependency on the MarkLogic Java Client version 5.1.0, which also depends on Java 9 or higher. ml-gradle 3.x depends on Java Client version 4.x.

This release also depends on ml-app-deployer 4.0.0; please be sure to read through the list of deprecated features that have been removed in that release.

In addition, this release addresses the following two issues:

• #528 mlLoadModules now loads all modules by default, instead of only loading new/modified modules. This behavior can be disabled by including "-x mlDeleteModuleTimestampsFile" when running mlLoadModules.
• #531 ml-gradle now depends on marklogic-unit-test 1.0.0 instead of 1.0.beta.

3.17.0

Highlights of issues addressed by this release:

• #397 and #527 Partitions and partition queries can now be deployed and also easily taken offline/online
• #521 Fix for writing the test results XML for nested test suites when running mlUnitTest
• Improvements in ml-app-deployer 3.17.0, including support for configuring SSL connections based on a JVM's default keystore

3.16.4

This release addresses a regression bug introduced in 3.16.3 - #523 , which is that mlClearModulesDatabase was failing when not used in a Data Hub project.