Releases: marklogic/ml-gradle
3.11.0
Summary of all issues:
- #415 Can now preview a deployment
- Support for faster deployment times via new properties for using the Configuration Management API (CMA) to deploy forests, amps, and privileges
- #400 Can now customize the DatabaseClient used by any DataMovementTask
- And see the release notes for ml-app-deployer 3.11.0 as well
3.10.2
3.10.1
This release contains a couple small enhancements in support of the upcoming DHF 4.1 release:
- #407 mlLoadSchemas now runs all commands in the "mlSchemaCommands" list
- #408 WatchTask now includes a method that can be overridden by a subclass which is called on every iteration of the loop
- Also includes ml-app-deployer 3.10.1, which is likewise in support of the upcoming DHF 4.1 release
3.10.0
Addresses 2 issues, along with a lot of changes in ml-app-deployer 3.10.0:
- #386 New mlDeleteResourceTimestampsFile task that is related to incremental deployments - see https://github.com/marklogic-community/ml-gradle/wiki/Incremental-deployment
- #394 The mlUnitTest task now depends on version 0.12.0 of marklogic-unit-test
- Initial support for incremental deployments to speed up deploying an application)
- And be sure to see the release notes for ml-app-deployer 3.10.0 which has some significant changes
3.9.0
Highlights from the full set of issues:
- #126 mlReloadSchemas no longer clears the schemas database; mlDeleteUserSchemas is instead used so that schema documents created via the deployment of resources such as temporal collections and view schemas are not deleted.
- #371 mlExportToFile can now write JSON documents to a valid JSON array, thanks to improvements in the marklogic-data-movement-components 1.1 release
- #372 mlNewProject no longer erroneously creates a REST API configuration file when no REST port is specified
- Improvements from ml-app-deployer 3.9.0
3.8.3
Bugfix release that provides a few fixes from ml-app-deployer and one small new feature in ml-gradle:
- #368 mlWatch now supports a callback for after modules are loaded
- Includes bug fixes from ml-app-deployer 3.8.3
3.8.2
This release has no changes in ml-gradle itself; it just depends on version 3.8.2 of ml-app-deployer which has a fix for allowing Data Hub Framework users to depend on a version of ml-app-deployer/ml-gradle higher than 3.6.3.
3.8.1
This release addresses the following issues:
- #360 The DatabaseClient connection used by mlUnitTest can now be fully configured - see the example project for instructions on how to do so
- #361 The task mlDeployRestApis was added
- And ml-app-deployer 3.8.1 includes a fix for deploying mimetypes and avoiding unnecessary restarts
3.8.0
Full set of issues, and the highlights are:
- #359 New CallResourceTask for simplifying calls to REST services
- #354 Fixed bug in mlWatch, introduced in 3.7.0, where it would stop running when a REST extension failed to load
- Improvements in ml-app-deployer 3.8.0, which includes a new property - mlOptimizeWithCma - to speed up forest creation when using ML 9.0-5 or higher. Also see this Resources Wiki page for documentation on inserting host certificates, which is another new feature in 3.8.0.
3.7.1
This is a bugfix release that updates the version of ml-unit-test used by ml-gradle from 0.10.0 to 0.11.1. It also includes:
- #352 Added support for -PrunCodeCoverage when running mlUnitTest
- A fix in ml-app-deployer 3.7.1