Releases: marklogic/ml-gradle
3.7.0
Summary of the full list of issues:
- #324 mlDatabaseDataDirectories now supports multiple data directories per host
- #333 New mlDeployConfigurations task for deploying configuration packages - requires MarkLogic 9.0-5+
- #349 New task "mlPrintForestPlan" for previewing what forests and replicas will be created for a database - see Creating forests for more information
- #351 mlDeleteAllTasks now honors mlGroupName
- Enhancements from ml-app-deployer 3.7.0
3.6.3
This release addresses two issues:
- #337 When running Gradle in daemon mode on Windows, file paths should always be resolved correctly from the project directory
- #339 This release now uses version 0.10.0 of ml-unit-test and provides control over whether teardown scripts are run or not
3.6.2
This is a small bugfix release that does include a new feature via ml-app-deployer 3.6.2 - list of issues is at https://github.com/marklogic-community/ml-gradle/issues?q=is%3Aclosed+milestone%3A3.6.2 , highlights:
- #326 mlRestartCluster uses the correct Manage API endpoint now for restarting a cluster
- #329 mlDeleteModuleTimestampsFile now pays attention to the value of mlModuleTimestampsPath
- #335 mlUndeployMimetypes was added
- And here's the list of changes in ml-app-deployer 3.6.2
3.6.1
This fixes an issue in ml-app-deployer where the 3.6.0 version of ml-app-deployer did not include support for the "mlHostGroups" property. No changes to ml-gradle other than it now depends on 3.6.1 of ml-app-deployer.
3.6.0
See the full set of issues for this release.
Highlights:
- #293 Can now assign hosts to groups via the new mlHostGroups property; see the Property reference for more info.
- #316 New tasks for generating resource templates - see Generating new resources for more info.
- #321 New task - mlPrintProperties - for printing all of the supported properties
- Improvements from ml-app-deployer 3.6.0
- #322 ml-gradle now depends on marklogic-data-movement-components for DMSDK support
- Improvements from ml-app-deployer 3.6.0
3.5.0
The main focus of this release is support for the ml-unit-test framework. See the link to the example project below for more information.
Issues:
- #277 Support for running ml-unit-test tests
- #178 Added example project for using ml-unit-test
- #313 New task for generating an ml-unit-test test suite
- Improvements from ml-app-deployer 3.5.0 and ml-javaclient-util 3.5.0
3.4.1
3.4.0
This release mostly involves the updates in 3.4.0 of ml-app-deployer, which includes several new properties for configuring your deployment process.
Key among those is that mlAdminUsername/mlAdminPassword have been deprecated in favor of mlSecurityUsername/mlSecurityPassword. Please see this Wiki page for more information.
In addition, SSL connections to ports 8001 and 8002 can be completed customized, as documented by this Wiki page.
This release also adds one new task to ml-gradle:
- #270 Can now update only the indexes of databases by running mlUpdateIndexes
3.3.1
This release features no changes to the ml-gradle codebase, but rather a bugfix in ml-javaclient-util and a small new feature in ml-app-deployer. See the ml-app-deployer 3.3.1 release notes for more information.
3.3.0
All issues - https://github.com/marklogic-community/ml-gradle/issues?q=is%3Aclosed+milestone%3A3.3.0
This release makes small changes to a couple existing tasks. First, the "mlClearContentDatabase" task now requires a property named "confirm" (instead of "deleteAll") to be set to "true". This is for consistency with the other change, which is that "mlUndeploy" now also requires that "confirm" be set to "true" (see #276). This pattern will be used for all tasks that benefit from some protection so that they're not accidentally run.
Highlights:
- Several new tasks for exporting data via DMSDK
- New task for clearing any database - #282
- New tasks for disabling/enabling all scheduled tasks - #281
- Improvements from ml-app-deployer 3.3.0