4.5.1

This bugfix release addresses a single issue:

• #650 ml-gradle tasks that didn't require authentication were failing when no authentication was provided. See the fix and writeup in the ml-app-deployer 4.5.1 release notes.

4.5.0

This minor release addresses the following items:

Security fixes

As mentioned in the ml-app-deployer 4.5.0 release notes, ml-gradle no longer defaults to a username of "admin" and a password of "admin" when connecting to MarkLogic. If you are setting at least mlUsername and mlPassword in your Gradle properties, you will not encounter any issues. If you are not, you simply need to set mlUsername and mlPassword in your Gradle properties (and you're free to set them to "admin" and "admin", though this behavior is discouraged in real world scenarios).

Bug fixes

• #645 mlPrintForestPlan no longer throws an error when custom forests are used.

New features

• #643 mlGenerateUnitTestSuite can now generate SJS test modules
• SAML, Kerberos, and Certificate authentication are now supported for all connections to MarkLogic; see the Property Reference for a list of new properties in 4.5.0 to support these authentication strategies.
• Supports connections for the upcoming MarkLogic Cloud release.

4.4.0

This minor release addresses the following items:

1. Depends on MarkLogic Java Client 6.0.0
2. Depends on ml-app-deployer 4.4.0
3. #625 Added mlDeployHostCertificateTemplates task
4. #636 mlNewProject prompts are more clear now
5. #637 Added mlDeploySecureCredentials
6. #642 Error is thrown instead of silent failure when task tries to invoke a command that does not exist

4.3.7

Bugfix release addressing the following items:

• Depends on ml-javaclient-util which bumps jackson-databind dependency to 2.12.7.1 to address CVE https://nvd.nist.gov/vuln/detail/CVE-2022-42004
• #628 mlNewProject no longer writes some files to Gradle daemon directory
• #629 Changed mlcp-example project to use logback

4.3.6

This patch release includes fixes from the following dependent libraries:

• ml-app-deployer 4.3.6
• ml-javaclient-util 4.3.6

4.3.5

This bugfix release addresses the following items:

• #617 mlDeleteModuleTimestampsFile now works properly on Gradle 6 and Gradle 7
• #612 mlExportWorkspaces now properly captures all qconsole workspace attributes
• Updated dependencies to minimize security vulnerabilities
• TDEs are now loaded via tde.templateBatchInsert when using MarkLogic 10.0-9 or higher
• Includes ml-app-deployer 4.3.4

4.3.4

• Bumping ml-app-deployer dependency to patch Spring4Shell

Full Changelog: 4.3.3...4.3.4

4.3.3

What's Changed

• update to latest CoRB release 2.5.3 by @hansenmc in #607
• Resolves issue #610 by @hansenmc in #611
• Patch for Spring4Shell

Full Changelog: 4.3.2...4.3.3

4.3.2

This bugfix release addresses the following issues:

• MlcpTask was fixed so that it can run on Gradle 6.4 or higher instead of 6.6 or higher
• ml-gradle 4.3.2 can now run on Gradle 6.4 and higher, and possibly Gradle 5.0 and higher as well (Gradle 4.x will not work due to a class conflict with the ML Java Client); this is due to modifying the mlShell task; the Wiki page on this task has been updated to reflect how to use it
• CallResourceTask can now be used on Gradle 7.x

4.3.1

This bugfix release addresses the following issues:

• #595 MlcpTask now works with Gradle 7.x
• And via ml-app-deployer 4.3.1, XML role files can now define capability queries