4.3.0

This release is focused on upgrading dependencies, in particular the ML Java Client to version 5.5.0:

• #138 Updated dependencies
• #134 and #139 - some code/javadoc cleanup

4.2.0

This is the first release that is published to Maven Central - https://search.maven.org/artifact/com.marklogic/ml-javaclient-util . Releases are no longer being published to jcenter since that has been deprecated.

This release does not have any functional changes, but it does bump up the version number of some of its dependencies:

• com.marklogic:marklogic-client-api = 5.3.2 to 5.4.0
• com.marklogic:marklogic-xcc = 10.0.5 to 10.0.6.2
• org.springframework:spring-context = 5.2.9.RELEASE to 5.3.7

4.1.1

This addresses a single issue:

• #132 Now depends on ML Java Client 5.3.2

4.1.0

This release upgrades all of its dependencies to the latest versions and runs on Java 8, matching its dependency on MarkLogic Java Client 5.3.0, which runs on Java 8 as well.

4.0.0

This major release is solely for depending on the MarkLogic Java Client version 5.1.0, instead of 4.x. Java Client 5 depends on Java 9 as well.

The only functional changes for this release were addressed by issue #129, in which the DocumentFile class no longer implements the Java Client DocumentWriteOperation interface, which changed in the 5.1.0 release. It instead has a new method for constructing a DocumentWriteOperation based on its data. In addition, the unused SimpleDocumentWriteOperation class was deleted.

3.14.0

This release adds the following two features:

• #127 Tokens can now be replaced in collections and permissions properties files
• #128 DefaultConfiguredDatabaseClientFactory is now able to construct an SSLContext and TrustManager based on a JVM's default keystore

3.13.4

This bugfix release addresses two issues:

• #121 DefaultSchemasLoader now uses one thread by default. This ensures that errors from loading invalid schema files are immediately thrown to the caller.
• #122 When catchExceptions = true on DefaultModulesLoader, errors from loading non-REST modules (typically invalid JSON files) are logged and not rethrown. This is useful for the mlWatch task in ml-gradle.

3.13.3

This release addresses one issue:

• #118 TDE validation no longer errs out when an XML template has processing instructions and/or comments in it. In addition, if a server error (as opposed to a validation error) occurs, the exception is no longer silently caught and logged, which is unlikely to be noticed.

3.13.2

This release addresses two issues:

• #119 The SimpleX509TrustManager class now both defaults to TLSv1.2 instead of SSLv3 and also accepts an argument for choosing the protocol to use
• #117 A friendlier error message is thrown when an invalid permissions string is passed into DefaultDocumentPermissionsParser

3.13.1

This release addresses a single issue:

• #116 The dependencies in build.gradle now use the proper, non-deprecated Gradle configurations