3.8.2

This is a small bugfix that addresses:

• #290 Restores a no-arg constructor on DeployForestsCommand. This allows users on Data Hub Framework 3.0.0 and possibly earlier to use this version of ml-app-deployer and ml-gradle (the no-arg constructor had been removed in version 3.7.0, thus limiting DHF users to version 3.6.3 or lower).

3.8.1

This release addresses a single issue:

• #287 If a mimetype is being updated but none of its properties differ from what's already set for the mimetype within MarkLogic, then the update call will not be made. This avoids an unnecessary restart, as the Manage API will trigger a restart any time a mimetype is updated, even if none of its properties changed.

3.8.0

Full set of issues, and the highlights are:

• #282 Can now insert host certificates
• #280 Forest creation can be optimized via the new mlOptimizeWithCma property
• Fixes in ml-javaclient-util 3.7.1 and ml-javaclient-util 3.8.0

3.7.1

This is a tiny bugfix release with one small fix:

• #279 There was typo in the name of the directory that ml-app-deployers checks for LSQT temporal collections - it was "lqst", it's now "lsqt"

3.7.0

Summary of the full list of issues:

• #264 Can now specify multiple data directories per mlDatabaseDataDirectories. Reworked how forests are created as well so there's now an ability to preview the forests that will be created.
• #268 New interface for customizing how forests and replicas are named
• #271 Configuration packages can now be deployed via the new /manage/v3 endpoint in MarkLogic 9.0-5
• #272 HTTP POST calls to the Manage API now use Spring's JSON UTF8 constant instead of just JSON
• #273 When an error occurs while loading REST modules, the error will be rethrown by default, causing the deployment to fail
• #274 Fixed bug with query rolesets and protected paths, where if mlSecurityUsername differed from mlManageUsername and mlManageUsername didn't have the security role, deploying these resources would fail
• Enhancements from ml-javaclient-util 3.7.0

3.6.3

This release fixes a single issue where, when running Gradle in daemon mode in Windows, file paths were not being resolved correctly from the project directory.

3.6.2

This is a small bugfix release that admittedly sneaks in a new feature too, as it was ready before other new features for 3.7.0 were ready - https://github.com/marklogic-community/ml-app-deployer/issues?q=is%3Aclosed+milestone%3A3.6.2

• #258 ELS endpoints now use the "mlSecurityUsername" user
• #260 Database resource defined by XML are now deployed/undeployed in the correct order (JSON was already supported)
• #261 (New feature that snuck in) Multiple sets of triggers can be deployed to different databases

3.6.1

This fixes an unfortunate merge issue that resulted in mlHostGroups not being supported in 3.6.0 - see #257

3.6.0

See the full set of issues for this release.

Summary:

• #249 New API for writing out templates for resources
• #253 Can now generate a list of all supported properties
• #255 Can now assign hosts to groups via the mlHostGroups property and AssignHostsToGroupsCommand
• #256 Now checks for a REST server via the servers endpoint instead of /v1/rest-apis
• Improvements in ml-javaclient-util 3.6.0

Also see the attached copy of the 3.6.0 deployer.jar .

3.5.1

This releases addresses the following items:

• Bug #248 is fixed, where mimetypes and groups couldn't be undeployed when the user doing the undeploying had already been deleted
• A new CLI is available - see https://github.com/marklogic-community/ml-app-deployer/wiki/Command-line-interface for more information. The executable jar for this is attached to this page.