Rob Rudin

Need to find a way to get the redaction validation message via the Java Client API - currently just getting the following: 17:03:22.071 [main] INFO c.m.a.c.schemas.LoadSchemasTest - MESSAGE: Local message:...

This may just need some research to see if it's a) working already, or b) we just need to bump up the dependency of the node-client-api.

@bshalke will verify

I found that I could do this via the REST Client plugin - e.g. I have this in a buffer: GET http://localhost:8011/v1/resources/marklogic-unit-test?rs:func=run&rs:suite=data-hub/5/smart-mastering/entity-matching/structured-property&rs:tests=singleValueArrayJsonMatch.sjs Authorization: Digest test-data-hub-developer password However, that requires a...

Here's what I'm doing for a fast code/test/fix cycle: 1. I'm using the above REST client plugin, and I have a buffer with the GET statement above. I modify that...

I wouldn't bother supporting "/ext" - there's really no use case for it, "/root" is the way to go.

For application modules, nearly all non-REST extensions will be / should be under src/main/ml-modules/root. Where it gets tricky is for test modules and bundles. Test modules are typically under src/test/ml-modules/root...

Users will configure mlModulePaths like this: mlModulePaths=src/main/ml-modules,src/test/ml-modules Then, in e.g. gradle-prod.properties, they'll just do this: mlModulePaths=src/main/ml-modules That provides a simple environment-based mechanism for determining whether to deploy test modules or...

Bundles will add the same complexity. What do you think of a feature in ml-gradle that denotes which paths under src/main/ml-modules/root should be ignored in a particular environment? That would...

Note that "/root" isn't part of the module URI. It's the directory in a module path that tells ml-gradle to load everything in it into the "root" directory - e.g....