4.0.3

This bugfix release addresses a single item:

• #412 No attempt is made to update query rolesets, as the Manage API in ML 10.0-4 no longer supports this, and it had no impact prior to that

4.0.2

This bugfix release addresses the following two items:

• #409 deleteTaskAtPath in TaskManager now works correctly (regression from 4.0.1, though did not impact ml-gradle or DHF at all)
• #410 PayloadParser now correctly excludes XML elements - e.g. in the context of excluding properties from an XML payload

4.0.1

This bugfix release addresses the following items:

• #404 The content-database.json file can now be ignored when undeploying an app so that the content database is left
• #406 Task uniqueness now takes "task-path" into account
• #408 The Database class now has a rangePathIndex property; the lack of this only had an impact when merging XML database files together (not common, as JSON is almost always used for resource files)

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-app-deployer 3.x depends on Java Client version 4.x.

In addition to depending on ml-javaclient-util 4.0.0, the following deprecated features in ml-app-deployer 3.x have been removed:

• The createTriggersDatabase property in AppConfig was deleted. If a triggers database should be created, a file should be created for it.
• getConfigDir was removed from AppConfig. This was a wrapper method around getFirstConfigDir(), and thus if a single ConfigDir is desired (AppConfig has a List), getFirstConfigDir() should be used.
• getSchemasPath and setSchemasPath were removed from AppConfig. getSchemaPaths and setSchemaPaths should be used.
• setDeployForestsWithCma, setDeployPrivilegesWithCma, and setDeployAmpsWithCma were all removed from AppConfig. These were all passthrough calls to methods on the CmaConfig object returned by getCmaConfig(), which should be used.
• The concept of "content database files" was removed from DeployOtherDatabasesCommand and ConfigDir. This provided a mechanism for defining multiple files for configuring a content database. DeployOtherDatabasesCommand is able to merge multiple files for any database, so this special-case feature was no longer needed.
• The commands DeployContentDatabaseCommand, DeploySchemasDatabaseCommand, and DeployTriggersDatabaseCommand have all been deleted, as DeployOtherDatabasesCommand handles all databases. The constants in SortOrderConstants used by this commands have also been deleted.
• GroupedReplicaBuilderStrategy was deleted, as DistributedReplicaBuilderStrategy is the proper strategy to use.
• The setDeployRolesInTwoPhases method was deleted from DeployRolesCommand, as that method no longer had any effect.
• The *AsAdmin methods in ManageClient have been deleted. *AsSecurityUser methods should be used.
• The adminUsername and adminPassword properties in ManageConfig were deleted. The securityUsername and securityPassword properties should be used instead.
• Based on the above changes, the following properties that had been deprecated in 3.x have been removed - mlAdminUsername, mlAdminPassword, mlConfigDir, and mlSchemasPath. Respectively, use mlSecurityUsername, mlSecurityPassword, mlConfigDirs, and mlSchemaPaths.

3.17.0

(Note that this tag was mistakenly applied initially on Dec 30, 2019, pointing at the last commit for 3.16.3. The ml-app-deployer 3.17.0 build was still published correctly to jcenter. This tag has since been recreated to point at the correct commit on master.)

Highlights of issues addressed by this release:

• #392 SSL connections for the Manage and Admin APIs and for REST servers can now be configured based on the JVM's default keystore
• #393 Privileges that reference roles that don't yet exist can now be deployed
• #394 Database partitions and partitions queries can now be deployed
• Improvements from ml-javaclient-util 3.14.0

3.16.3

This release just bumps the ml-javaclient-util dependency from 3.13.3 to 3.13.4.

3.16.2

This release address the following items:

• #389 Forest replicas are now properly distributed when a host has more than one forest for a database
• #388 Invalid property values result in an exception message that identifies the property name and value
• #386 The logging for when a call is made using the "security" user is now correct
• #384 Additional properties were added to the Database object (only relevant if you're using XML files for databases)

3.16.1

Bugfix release addressing two issues:

• #378 Tokens are now properly replaced while loading schemas
• #382 mlDatabasesWithForestsOnOneHost works properly with mlDatabaseGroups now

3.16.0

Highlights of all issues addressed by this release:

• #367 Scheduled tasks can now have any property "updated", which amounts to the task being deleted and then recreated (as the Manage API only allows for updating task-enabled)
• #370 TLSv1.2 is now the default protocol for secure connections. This can be customized via the mlSimpleSsl and mlAppServicesSimpleSsl properties by setting their values to the desired protocol (instead of "true" or "false").
• #371 Multiple paths can now be specified when setting mlDatabaseReplicaDataDirectories
• #372 Forests are now created properly when the existing forests are not evenly distributed across a cluster (as is the case after adding a new host)
• #374 Database-specific resources can now be associated with a database via the name of the database file for that database
• And one bugfix from ml-javaclient-util 3.13.3 - TDE validation now properly handles XML templates with processing instructions and comments. Also note that if any error occurs when validating a TDE template - not just a validation error - the error will cause a failure instead of being silently logged.

3.15.1

This release addresses the following issues:

• #364 The dependencies in build.gradle now use the proper, non-deprecated Gradle configurations
• #366 The 4 users that ML creates when it's initialized will not be undeployed by default if you have user files that modify these users
• #368 A bug with database ordering was fixed (database ordering now uses the same topological sort approach that role ordering uses)
• Includes fixes in ml-javaclient-util 3.13.1