Support for mlConfigPaths and mlModulePaths properties like ml-gradle has

[peetkes]

We are working on a dhf implementation where we have two different sets of configs, modules and plugins that we want to deploy on ML.
In teh current situation dhf does not honour these properties.
It will show them on the console but id does not act upon them.

We also have some specific indexes for the different databases (like temporal config), where would you typically put them so as the dhf will merge the entity-config, the hub-internal-config and the user specific configs? Now the final database config is in the src/main/ml-config/databases folder where I would expect it to be in the hub-internal-config folder.

[grechaw]

I don't know particular answers, but in general src/main/hub-internal-config all configures the staging db, and src/main/ml-config all configures the final db. There are exceptions due to how the DHF is bootstrapped.

DHF is very much tied to a single project/deployment. You could experiment with having two separate projects deploy to the same database, but I have no idea what might happen in this circumstance.

I do think it makes sense to support more than one project -- please talk to @sbayatpur-ml about your needs in this regard.

[peetkes]

Problem with two different projects pointing to the same db is that all the mlRe.. tasks start with clearing databases rendering these tasks useless for multiple projects. I also think that there is a large gap between what ml-graldle offers and what dhf offers with respect to configuration. It would be a nice thing if this gap can be closed as soon as possible.

[peetkes]

And it is not so much as two different projects but two different upstream systems with their own config and modules ending up in the same database in MarkLogic.
Btw I noticed that 4.0.3 honors the mlModulePaths property of ml-gradle so I would suggest to do the same with mlConfigPaths. It would make life so much easier

[kkanthet]

Fixed as part of Release 4.1.0