Mads Hansen
An issue that we ran into is that over time we have accumulated triggers that may either be renamed or removed between deployments. We don't want to perform an `mlClearTriggersDatabase`,...
While investigating issues reported for issue #373 I was having trouble reproducing the symptoms. It turned out that the dependencies in the example/corb build.gradle had an old version of ml-gradle...
- removed reference to jcenter as a repo, since it's dead. - updated instructions for running JUnit tests to reference the marklogic-client-api subproject
On Maven Central, the MarkLogic Client API description is: `$project.description`. https://mvnrepository.com/artifact/com.marklogic/marklogic-client-api It had a more descriptive description when we had published under https://mvnrepository.com/artifact/com.marklogic/java-client-api. We might need to check the pom...
It would be helpful to report and visualize code coverage for the modules that are tested by Roxy Unit Tests. This would help highlight areas that have not (yet) been...
When a job is configured to use `ExportToFileTask` or `ExportBatchToFileTask` and does not have a **PROCESS-MODULE** configured, then there is nothing to execute or write and the job finishes quickly....
`javax.xml.bind.DatatypeConverter` is deprecated and removed in Java 11. Will need to either add the necessary JAXB dependency or modules, or look to use the `java.util.Base64` class instead. Build issues observed...
The current set of tests function mostly as integration tests that require a live instance of MarkLogic, and take ~15 minutes to run. - Unit tests should run quickly, and...
When **EXPORT-FILE-NAME** option is specified, the `ExportBatchToFileTask` is enabled. Users have encountered a situation in which the **EXPORT-FILE-NAME** option was specified with a blank/empty value (expecting no export file to...