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.

3.16.3

This bugfix release addresses the following issues:

• #373 CorbTask now works correctly on Gradle 5
• #498 Refactored mlUpdateIndexes, mlWatch, and mlClearModulesDatabase so that Data Hub can modify these tasks without replacing them (task replacement is not supported in Gradle 6)
• #507 mlCreateTransform and mlCreateResource now creates modules in the first non-mlBundle/mlRestApi module path defined by mlModulePaths
• #519 mlClearTriggersDatabase prints a message suggesting the use of mlClearDatabase instead

In addition, this includes two fixes from ml-javaclient-util 3.13.4.

3.16.2

This release just incorporates changes from ml-app-deployer 3.16.2.

3.16.1

Bugfix release that addresses two issues:

• #500 mlNewProject and mlScaffold should write files to the correct paths now on Gradle 5.5+ and Java 11/12
• #504 mlDeleteForestReplicas requires confirmation to run now
• And a couple fixes in ml-app-deployer 3.16.1 too

3.16.0

This release only has changes in the libraries that ml-gradle depends on, not in ml-gradle itself:

• See the release notes for ml-app-deployer 3.16.0
• And see the release notes for ml-javaclient-util 3.13.3

3.15.2

This bugfix release addresses the following issues:

• #476 mlDeleteCollections now handles "-Pcollections" correctly
• #483 A typo in the task description for mlUnitTest was corrected
• Includes fixes in ml-app-deployer 3.15.1

3.15.1

This is a bugfix release addressing a single issue:

• #472 Preparing bundles - i.e. mlPrepareBundles - now works properly on Java 11+. This is important for e.g. any marklogic-unit-test users running on Java 11+.

3.15.0

The main focus of this release is the additional support in ml-app-deployer for using the Configuration Management API (please see the note in there for how to configure CMA usage based on the version of MarkLogic you're using). Please see the release notes for ml-app-deployer 3.15.0 for more information.

Issues addressed within ml-gradle in this release:

• #464 mlNewProject now works correctly on Java 12+
• #467 Now depends on the latest release of marklogic-unit-test