Releases: marklogic/ml-gradle
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
3.15.1
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:
3.14.0
This release of ml-gradle includes significant changes within ml-app-deployer 3.14.0 for how databases are deployed. These changes were made for supporting resource files in bundles (see below) as well as laying the groundwork for further usage of the MarkLogic Configuration Management API for speeding up the deployment of applications by including as many resources as possible in a single request. The latter support should be available in the 3.15.0 releases of ml-gradle and ml-app-deployer.
All issues addressed by this release:
- #449 ServerEvalTask now has a client property to allow for customizing the DatabaseClient that it uses
- #451 Added mlNewTrigger for generating a new trigger file
- #453 mlInstallAdmin now accepts a parameter for the realm
- #454 Bundles now support an ml-config directory for resources. See Bundles for more information. Note that this includes support for merging certain resource types as well.
- #456 Multiple instances of DeleteCollectionsTask can now be invoked at once
3.13.0
Highlights from the full set of changes:
- #420 mlRestApi is now named mlBundle; see the docs on bundles for more information
- #446 Loading data is now part of a deployment, and data can also be loaded from a bundle
- #447 Installing system plugins is now part of a deployment, and plugins can also be loaded from a bundle
- #448 Schemas can now be loaded from a bundle
- And see the list of changes in ml-app-deployer 3.13.0
3.12.0
This release addresses the following items:
- #428 ml-gradle now resolves file paths correctly when run using Java 11 with the Gradle daemon enabled. See "mlIgnoreProjectDir" in the Property Reference if you need to disable this functionality because you're using absolute paths for property values.
- #423 A database and all of its forests can now be deleted via mlDeleteDatabase (which requires -Pconfirm=true as a safety measure)
- #421 MlcpTask now allows for a custom DatabaseClient to be used for logging output
- #419 DMSDK jobs that accept a "transform" parameter can now accept a transform name plus parameter names and values
- #418 CopySearchOptionsTask simplifies copying search options so that they're available via multiple REST servers
- #416 mlReloadSchemas was fixed so that it does not clear a content database
- Also includes enhancements from ml-app-deployer 3.12.0 and marklogic-data-movement-components 1.2.0